Part of a Data Solution

Postal Codes Solution
Every worldwide postal-code dataset in one bundle — the ultimate global reference for precise postal codes.
Explore →

Premium

You're viewing a free sample

Get the complete dataset — all rows and files — delivered instantly after checkout, with lifetime access to the latest version.

Secure checkout via Stripe
Instant download after payment
Lifetime access to the latest version
Creative Commons Attribution 4.0 International license

20% off

$49.90$39.92

one-time payment

Download sample · CSV · 13.5 kB Report an Issue

API Access

Access dataset files directly from scripts, code, or AI agents.

Browse dataset files

Dataset Files

Each file has a stable URL (r-link) that you can use directly in scripts, apps, or AI agents. These URLs are permanent and safe to hardcode.

/logistics/postal-codes-bg/

├ .licensing-notes.md

https://datahub.io/logistics/postal-codes-bg/_r/-/.licensing-notes.md

├ .migration-notes.md

https://datahub.io/logistics/postal-codes-bg/_r/-/.migration-notes.md

├ ATTRIBUTION.txt

https://datahub.io/logistics/postal-codes-bg/_r/-/ATTRIBUTION.txt

├ README.md

https://datahub.io/logistics/postal-codes-bg/_r/-/README.md

└ datapackage.yaml

https://datahub.io/logistics/postal-codes-bg/_r/-/datapackage.yaml

Key Files

Start with these files — they give you everything you need to understand and access the dataset.

datapackage.yaml— metadata & schema

https://datahub.io/logistics/postal-codes-bg/_r/-/datapackage.yaml

README.md— documentation

https://datahub.io/logistics/postal-codes-bg/_r/-/README.md

Typical Usage

1. Fetch datapackage.yaml to inspect schema and resources
2. Download data resources listed in datapackage.yaml
3. Read README.md for full context

Data Files

postal-codes-bg-sample

Field	Type	Description	Constraints	Title
country_code	string	ISO 3166-1 alpha-2 -- always BG		Country Code
postal_code	string	Bulgarian postal code (4 digits)	{ "pattern": "^\\d{4}$" }	Postal Code
place_name	string	Locality/place name, bilingual Cyrillic / Latin-transliteration (e.g. "Aitos / Ajtos")		Place Name
admin_name1	string	Oblast (province) -- 28/28 covered, bilingual Cyrillic / Latin		Administrative Name 1
admin_code1	string	ISO 3166-2:BG code		Administrative Code 1
admin_name2	string	Obshtina (municipality) -- 265 distinct values, bilingual		Administrative Name 2
admin_code2	string	GeoNames' own municipality code		Administrative Code 2
admin_name3	string	Settlement within municipality -- partially populated, a genuine source gap		Administrative Name 3
admin_code3	string	GeoNames' own settlement code		Administrative Code 3
latitude	number	GeoNames latitude (WGS84)		Latitude
longitude	number	GeoNames longitude (WGS84)		Longitude
accuracy	string	GeoNames accuracy of latitude/longitude. GeoNames documents 1=estimated, 4=geonameid, 6=centroid of addresses or shape; other values (e.g. 3) occur upstream without documentation. Empty where GeoNames gives none.		Accuracy
alternative_city_name	string	Not populated in this release		Alternative City Name

Download

Download sample CSV

About

Last updated: 2 October 2026
Total rows: 100
Format: CSV
File size: 13.5 kB
Source: GeoNames postal code database -- Bulgaria (BG)
License: Creative Commons Attribution 4.0 International

About this dataset

Postal Codes Dataset for Bulgaria (BG)

This dataset lists Bulgarian postal codes with place names, oblasts (all of them), municipalities, settlements and WGS84 coordinates. Place and administrative names are bilingual Cyrillic/Latin.

Column definitions, row count, size and last-updated date are in datapackage.yaml.

Data Sources

Postal codes, place names, administrative divisions and coordinates: © GeoNames, postal code export for Bulgaria, CC BY 4.0.

Changes made to the source data: oblast codes (admin_code1) written as ISO 3166-2:BG codes (BG-01 to BG-28) by crosswalk from the GeoNames codes, and one corrupted duplicate source row for postal code 6045 dropped (it assigned the code to Smolyan oblast / Devin municipality while a self-consistent Stara Zagora row for the same code remained).

Not endorsed by, or affiliated with, GeoNames. See ATTRIBUTION.txt for the full attribution notice.

Known limitations

Names are bilingual, Cyrillic and Latin transliteration separated by " / " (for example "Айтос / Ajtos"), kept as the source gives them.
admin_name3 (settlement within municipality) is populated on only part of the rows. This is a gap in the source.
A (postal_code, place_name) pair can repeat because the same code and name belong to different villages in different municipalities, or to a municipality seat and a settlement within it. The primary key is (postal_code, place_name, admin_code2, admin_code3).
alternative_city_name is not populated.

Usage

The dataset files are available in CSV format and can be accessed and downloaded using the links provided in datapackage.yaml.

For other inquiries, contact datahub@datopian.com