IBAN example · TR

Turkish IBAN example

Use this Turkish example to inspect the 26-character layout and MOD 97 result. This example is intended only for format and checksum testing. Account existence and ownership have not been verified. Do not use it for real payments. For end-to-end payment testing, use your payment provider’s official sandbox fixtures.

Sample IBAN
TR33 0006 1005 1978 6457 8413 26
TR330006100519786457841326

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.

Country code
ISO 3166 — Turkey
TR
Check digits
MOD 97-10 checksum
33
BBAN field 1
5 digits · digits (0–9)
00061
BBAN field 2
1 character · alphanumeric (A–Z, 0–9)
0
BBAN field 3
16 characters · alphanumeric (A–Z, 0–9)
0519786457841326

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.

TR 33 00061 0 0519 7864 5784 1326
Country
TR · 2
Check
2 digits
Bank code
5 digits
Reserved
1 char (0)
Account
16 chars

The five-digit bank code is the key that ties the IBAN to a specific Turkish bank — Ziraat is 00061, Garanti BBVA is 00062, Akbank is 00046, İş Bankası is 00064. The reserved character is always 0 today and is reserved for future use by the Turkish Banks Association.

Turkish parser test fixtures

These examples test length, character structure and MOD 97 only. Bank-code assignments, account existence and ownership have not been verified. Do not use them for real payments. Use your payment provider’s official sandbox fixtures for end-to-end tests.

FixtureBank codeSample IBAN (26 chars)
Test fixture A00061TR33 0006 1005 1978 6457 8413 26
Test fixture B00062TR74 0006 2005 1978 6457 8413 26
Test fixture C00046TR97 0004 6005 1978 6457 8413 26
Test fixture D00064TR59 0006 4005 1978 6457 8413 26
Test fixture A
TR330006100519786457841326
Test fixture B
TR740006200519786457841326
Test fixture C
TR970004600519786457841326
Test fixture D
TR590006400519786457841326

⚠️ These are synthetic test IBANs that pass MOD 97 but account existence and ownership have not been verified. 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, use your payment provider’s official sandbox IBAN and BIC fixtures instead of pairing this example with a real bank’s BIC.

Search or validate this complete TR IBAN

Copy the complete string TR330006100519786457841326 or load it directly in the validator. The validator detects Turkey from the TRprefix, checks the 26-character length, and runs the MOD 97 checksum in your browser.

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 inspect the character classes and boundaries of the 5!n1!c16!c pattern; semantic bank and account assignments need a national specification — and that is exactly what the field-by-field breakdown below shows.

Copyable validator test cases

Expected results apply to the checks implemented by this site. Select and copy the tab-separated data for local tests. They say nothing about account existence, ownership or payment readiness.

Testing with this Turkish IBAN

Use the fixture in local form and checksum tests: accept the grouped lowercase form after normalization, reject a missing character, reject an illegal symbol, and reject a changed check digit. A country-pattern test should also reject letters in numeric BBAN fields even if the checksum has been recomputed. This example is intended only for format and checksum testing. Account existence and ownership have not been verified. Do not use it for real payments. For end-to-end payment testing, use your payment provider’s official sandbox fixtures.

Turkish IBAN example and SWIFT codes

No BIC is assigned to this test fixture. For local parser tests, test IBAN and BIC syntax separately. For end-to-end payment tests, use your payment provider’s official sandbox fixtures. For a real payment, obtain the complete instruction from the beneficiary’s bank.

Turkish IBAN example FAQ

Is this Turkish IBAN example real?
Account status is unknown. It is an example intended to pass MOD 97 and the 26-character TR length check. This example is intended only for format and checksum testing. Account existence and ownership have not been verified. Do not use it for real payments. For end-to-end payment testing, use your payment provider’s official sandbox fixtures.
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 using customer-supplied data; account existence is not verified.
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. Do not use this example for a wire. Obtain the complete IBAN and BIC from the beneficiary’s bank.
⚠️ This is a synthetic test IBAN. It passes format and MOD 97 checks but has not been checked for account existence or ownership. Do not use it for real payments. Use official provider sandbox fixtures for end-to-end payment tests.
Turkish IBAN overview →TR IBAN format specValidate this example

Reference scope: bundled country length and BBAN character pattern. A registry version and entry-by-entry source review are not recorded for this release. National domestic checksums, bank-code assignments, account existence and ownership are not verified.