Egypt IBAN Generator
Free test EG IBANs: 29 characters, official registry format, valid check digits.
Egypt IBAN generator
29-character format, official registry structure.
Same country + seed + row order gives the same test values. Leave blank for random samples. Seed algorithm: v1. Do not enter personal data.
Egypt IBAN format
A Egypt IBAN is 29 characters long: the EG country code, 2 check digits, and a 25-character BBAN (4 digits + 4 digits + 17 digits). Here is how a generated test IBAN breaks down:
| Part | Example | Format |
|---|---|---|
| Country code | EG | 2 letters (ISO 3166) |
| Check digits | 40 | 2 digits: mod-97 checksum |
| Bank code | 0120 | 4 digits |
| Branch code | 1468 | 4 digits |
| Account number | 75064712439500980 | 17 digits |
Full test IBAN: EG40 0120 1468 7506 4712 4395 0098 0 (random test value)
About Egypt IBANs
- Egypt's 29-character IBAN: 4-digit bank code + 4-digit branch code + 17-digit account number.
- Egypt adopted IBAN to streamline Suez Canal: era correspondent flows into straight-through processing.
- The Central Bank of Egypt publishes the official bank-code list.
Use test Egypt IBANs for
- Testing payment forms that accept Egypt bank details.
- QA fixtures and demo data with the correct 29-character structure.
- Validating your own mod-97 implementation against known-correct outputs.
Country-specific testing notes
The layout contains separate bank and branch fields followed by the account component. Do not confuse the complete IBAN with a shorter domestic account field.
Test more than the happy path
Generate with seed country-regression-v1, preserve the selected country and quantity, then run again to reproduce the same rows. Include an invalid-checksum input and a shorter input in your form tests. The versioned fixture pack supplies expected results for the implemented format checks.
Interpret the result correctly
Our checks cover the registered length, character pattern and international check digits. They do not certify domestic checksums, reserved-value rules, active bank codes, account existence or recipient ownership. Use bank-issued details for payments and your provider’s documented sandbox values for integration tests.