Official Ministry draftSnapshot at 1 June 2025
≈51,985Unresolved citizenship files
Published in a Ministry draft document; not a live queue or final administrative report.
Read the source recordMenu
Movement radar
See what is moving. Know what the evidence can—and cannot—say.
Official activity is available now. Applicant updates without direct identifiers become a comparison only when enough matching files report movement.
No name · No case number · No Ministry PIN · Month-level dates only
Report your statusOfficial activity
Real output, clearly separated from your personal timeline.
These published totals prove that the system is active. They do not reveal a live queue or which filing month is next.
OfficialCalendar year 2025
23,465Cases reviewed by the Citizenship Council
Reviewed does not mean approved.
Read the source recordPrepiska analysisJanuary–June 2026
7,036Citizenship acquisitions
Prepiska calculation from Q1 and Q2 Presidency reports.
Read the source recordOfficial
The published legal timing reference
Article 35 sets a target for the Ministry’s proposal stage—not a prediction of your final decision.
Bulgarian-origin route
General, parent and marriage routes
Restoration and release
Last official-data review: 2026-07-26
Open-source intake
What the public record can—and cannot—tell us.
Official publications drive the official figures. Facebook and Telegram communities add a separate crowd-sourced layer: shared experience, recurring questions and unfamiliar status wording. Structured opt-in reports—not copied personal posts—can support aggregate movement signals.
Official dataCrowd-sourced community Excluded from tracker
H1 2026 Presidency outcomes
7,036 acquisitions and 1,280 refusals, calculated from the official Q1 and Q2 reports.
Inspect source Official guidanceAlbania application guidance
The Bulgarian Embassy in Tirana published a practical Article 15 document checklist. It improves the manual, not the queue model.
Inspect sourceFacebook and Telegram applicant communities
These communities often provide honest peer help and surface real procedural problems. Prepiska uses only structured opt-in reports: small cells stay hidden, one connection is rate-limited, and a management key updates an existing report. These controls reduce—never eliminate—manipulation.
Verified public entry points · checked 26 July 2026Current country backlog or latest file number
No recurring official publication provides it. A 2026 access-to-information record says the requested extraction does not exist as recorded public data.
Inspect sourceCommunity posts are not copied into the tracker. The public links below do not imply endorsement, and login-only Facebook groups are not listed without a stable verified link. Never post a case number, Ministry PIN or document there.
Applicant-reported movement
Compare only like with like.
Choose a legal route and filing year. Small groups stay hidden. Displayed time ranges span the 20th–80th percentiles of usable completed transitions.
Cohort year uses Ministry registration when provided; otherwise it uses the interview year. Reports are self-reported, not identity or document verified, and may reflect self-selection or manipulation. Counts are rounded and may not sum.
Loading grouped reports…
No personal queue position. No promise of approval. No estimate from decree totals.
One privacy-protected checkpoint
Help reveal movement without revealing yourself.
Share only month-level procedure facts. The key is stored only here; the server receives it for updates but keeps only a one-way hash.
Restore an earlier contribution
Use the alias and private key from your recovery file. They are checked directly; Prepiska cannot recover a lost key.