Turkish IBAN example

Field-by-field breakdown

The breakdown below splits the sample Turkish IBAN (TR330006100519786457841326) into its country code, check digits, and BBAN fields, applying the 5!n1!c16!c pattern so each field is labeled with its length and allowed characters. This is the same field-by-field view the IBAN validator produces for any TR IBAN you paste, so you can compare a real Turkish IBAN against this reference structure.

Turkish IBAN format — 26 characters, block by block

A Turkish IBAN is always 26 characters and follows the structure TR + 2 check + 5 bank + 1 reserved + 16 account. In the human-readable grouping defined by ISO 13616 it looks like TRXX 0000 6XXX XXXX XXXX XXXX XX — four-character blocks separated by spaces, with the last block holding the final two characters. The spaces are presentation only; the stored IBAN is 26 characters with no spaces.

Turkish IBAN examples for the top 4 banks

The five-digit bank code at positions 5–9 of a Turkish IBAN tells you which bank holds the account. The table below gives a MOD 97-valid sample IBAN for each of Turkey's four largest banks, alongside the bank's SWIFT/BIC code. Use these for payment-form tests and demos — they are synthetic and do not map to real accounts.

⚠️ These are synthetic test IBANs that pass MOD 97 but do not belong to any real account. Never send money to them.

Common Turkish IBAN mistakes (the 24 vs 26 myth)

The single most common mistake with Turkish IBANs is miscounting the length as 24 characters. A Turkish IBAN is 26 characters, not 24. The confusion usually comes from dropping the two MOD 97 check digits at positions 3–4, or from comparing against a 24-character IBAN from another country (for example, no major IBAN country uses exactly 24, but several use 22 or 23, which adds to the confusion). If a form rejects a Turkish IBAN for being the wrong length, count again — it should be 26.

• Length is 26, not 24. The structure is TR + 2 check + 5 bank + 1 reserved + 16 account = 26. Dropping the check digits or the reserved character is what makes people think it is 24.
• Spaces don't count. The human-readable grouping TRXX 0000 6XXX XXXX XXXX XXXX XX contains spaces for readability; the real IBAN stored and validated is 26 characters with no spaces.
• Country code is TR, not TK. TK is the deprecated ISO 3166 code for Tokelau; Turkey has always been TR in IBAN.
• The reserved character is 0. Position 10 is currently always 0; do not put a 1 or a bank-specific digit there — it will fail validation.
• Bank code is 5 digits, not 4. The bank code at positions 5–9 is five digits (e.g. 00061 for Ziraat); a 4-digit domestic branch code is a different identifier and does not belong in the IBAN.

How to use this Turkish IBAN example

A common use case is testing a payment form that accepts Turkish IBANs: paste the sample into your form to confirm it accepts 26-character TR input and rejects malformed values. You can also load this example straight into the IBAN validator to see the green check, or open the Turkish IBAN format page for the full structure spec. For end-to-end testing of a cross-border flow, pair this IBAN with the receiving bank's SWIFT/BIC code.

Reading the Turkish IBAN structure

Reading the sample Turkish IBAN left to right: the first two characters (TR) are the ISO 3166 country code for Turkey; the next two are the MOD 97 check digits, chosen so the whole number passes the checksum; and the remaining 22 characters are the BBAN, which encodes the bank and account under Turkey's national format. Because the BBAN layout is fixed for Turkey, you can predict which characters are the bank code and which are the account number just from the 5!n1!c16!c pattern — and that is exactly what the field-by-field breakdown below shows.

Testing with this Turkish IBAN

For QA and integration work, this Turkish IBAN example is most useful in three places. In a payment form, paste it to confirm the field accepts 26-character TR input and rejects values that are too short, too long, or have a bad country prefix. In a MOD 97 unit test, assert that the example returns a remainder of 1 and that flipping any single digit makes it fail. In an end-to-end test, pair the IBAN with a Turkey SWIFT/BIC code so the full wire payload looks realistic. Because the example is synthetic, it will never collide with a real Turkey account, which makes it safe to commit to test fixtures.

Turkish IBAN example and SWIFT codes

If you are testing a full international payment into Turkey, you will usually need a SWIFT/BIC code alongside this IBAN. The Turkey SWIFT codes page lists the major Turkey banks and their head-office BICs, so you can build a realistic TR wire payload around this Turkish IBAN.

Turkish IBAN example FAQ

Is this Turkish IBAN example real?

No. It is a synthetic value generated to pass MOD 97 and the 26-character TR length check. It does not correspond to any real Turkey bank account, so it is safe for test fixtures and demos but must never be used for an actual transfer.

Why use a synthetic Turkish IBAN instead of a real one?

Real Turkish IBANs are private account identifiers; publishing one would expose a customer's account. A MOD 97-valid synthetic example gives you the same format and checksum behavior for testing without touching any real account.

Can I load this TR example into the validator?

Yes. The "Validate this example" link below loads this sample straight into the IBAN validator so you can see the green check and the full breakdown, exactly as a real Turkish IBAN would render.

What do I pair with a Turkish IBAN for a wire?

For most cross-border payments into Turkey you need the IBAN plus the receiving bank's SWIFT/BIC code. This Turkish IBAN example covers the account side; look up the bank's BIC separately to complete the wire instructions.