Branch SWIFT code

ESSEDE5F513 | DSK Hyp SWIFT/BIC Code

Use ESSEDE5F513 to identify DSK Hyp in Gießen, Germany for international transfers.

BRANCH / OFFICE
SWIFT / BIC
ESSEDE5F513
Bank
DSK Hyp
Office
Branch / office
City
Gießen
Country
Germany
Address
Not provided, 35390
IBAN length
22 characters
Currency
EUR
Data source

Central bank registries and SEPA data. See our methodology.

IBAN validator

Validate a DSK Hyp IBAN

Check the structure and checksum, then resolve the bank and branch details against our registry.

3 free checks a day
READY
// enter an IBAN to see the validation response
Code anatomy

What ESSEDE5F513 identifies

ESSE DE 5F 513
Bank code
ESSE
Country code
DE
Location code
5F
Branch code
513

An 8-character code or an 11-character code ending in XXX identifies the primary office. Other 11-character endings identify a branch or office.

Branch directory

Other DSK Hyp branches

15 other branch records in Germany, with head offices listed first.

Showing 1–15
ESSEDE5F Frankfurt am Main Frankfurt am Main Head office ESSEDE5F390 Aachen Aachen Branch ESSEDE5F100 Berlin Berlin Branch ESSEDE5F440 Dortmund Dortmund Branch ESSEDE5F300 Düsseldorf Düsseldorf Branch ESSEDE5F360 Essen Essen Branch ESSEDE5F512 Frankfurt am Main Frankfurt am Main Branch ESSEDE5F200 Hamburg Hamburg Branch ESSEDE5F370 Köln Köln Branch ESSEDE5F860 Leipzig Leipzig Branch ESSEDE5F550 Mainz Mainz Branch ESSEDE5F700 München München Branch ESSEDE5F760 Nürnberg Nürnberg Branch ESSEDE5F130 Rostock Rostock Branch ESSEDE5F600 Stuttgart Stuttgart Branch
SWIFT / BIC guide

Common questions about ESSEDE5F513

Branch-specific answers for this DSK Hyp record.

What is the SWIFT/BIC code for DSK Hyp?

The SWIFT/BIC code for DSK Hyp in Gießen, Germany is ESSEDE5F513.

Is ESSEDE5F513 a head office or branch code?

This code identifies a specific branch or office. Always confirm the code with the recipient before sending a transfer.

How long is an IBAN in Germany?

An IBAN in Germany contains 22 characters. A valid length alone does not guarantee a valid account, so use the validator above to check the structure and checksum.

Found a problem with this branch record? Report it without changing or merging the underlying branch entry.

Report a data issue