Telegram RegisterThe public register of Telegram
Telegram profile photo for Sobirapp Birthdays

Bot

Sobirapp Birthdays

@sobirapp_bot

On this record: Topic · Growth · Engagement · Citations · Cite this entry

37,126monthly users

+4,654 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID752259676
TypeBot
Username@sobirapp_bot
First recorded13 August 2026
Last confirmed live26 October 2026
Measurements held40
Confirmed unchanged1 time, most recently 26 October 2026
On Telegramt.me/sobirapp_bot

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 97% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

31,97141,41436,692.57 August 2026 — 32,472 monthly users8 August 2026 — 32,426 monthly users9 August 2026 — 32,448 monthly users10 August 2026 — 32,368 monthly users11 August 2026 — 32,377 monthly users13 August 2026 — 32,377 monthly users13 August 2026 — 32,379 monthly users15 August 2026 — 32,553 monthly users16 August 2026 — 32,520 monthly users17 August 2026 — 32,446 monthly users18 August 2026 — 32,525 monthly users19 August 2026 — 32,535 monthly users20 August 2026 — 32,703 monthly users23 August 2026 — 32,770 monthly users25 August 2026 — 32,500 monthly users26 August 2026 — 32,545 monthly users27 August 2026 — 31,971 monthly users29 August 2026 — 33,406 monthly users31 August 2026 — 33,479 monthly users2 September 2026 — 34,150 monthly users3 September 2026 — 35,804 monthly users8 September 2026 — 37,467 monthly users11 September 2026 — 38,749 monthly users12 September 2026 — 39,260 monthly users14 September 2026 — 39,266 monthly users16 September 2026 — 39,365 monthly users18 September 2026 — 40,306 monthly users1 October 2026 — 41,414 monthly users6 October 2026 — 40,520 monthly users10 October 2026 — 39,431 monthly users13 October 2026 — 38,685 monthly users15 October 2026 — 37,616 monthly users16 October 2026 — 38,768 monthly users17 October 2026 — 38,647 monthly users18 October 2026 — 38,264 monthly users19 October 2026 — 38,003 monthly users21 October 2026 — 37,883 monthly users22 October 2026 — 37,858 monthly users24 October 2026 — 37,473 monthly users26 October 2026 — 37,126 monthly users37,1267 August 202626 October 2026
40 measurements spanning 79 days, net +4,654. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 30,555–42,830 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 40
Measured (UTC)Monthly usersChange
26 Oct 2026, 02:3837,126-347
24 Oct 2026, 08:5937,473-385
22 Oct 2026, 12:1737,858-25
21 Oct 2026, 02:4037,883-120
19 Oct 2026, 23:4638,003-261
18 Oct 2026, 21:3738,264-383
17 Oct 2026, 18:5038,647-121
16 Oct 2026, 19:3638,768+1,152
15 Oct 2026, 21:5637,616-1,069
13 Oct 2026, 23:2738,685-746
10 Oct 2026, 22:0139,431-1,089
6 Oct 2026, 16:1940,520-894
1 Oct 2026, 17:5941,414+1,108
18 Sept 2026, 11:4040,306+941
16 Sept 2026, 01:5939,365+99
14 Sept 2026, 11:5939,266+6
12 Sept 2026, 23:0139,260+511
11 Sept 2026, 02:4138,749+1,282
8 Sept 2026, 05:5737,467+1,663
3 Sept 2026, 08:3235,804first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 26 October 2026 — this entry's latest reading, not the date you are reading this.

“Sobirapp Birthdays” (@sobirapp_bot), 37,126 monthly users as measured 26 October 2026. Telegram Register, tgregister.com/channel/sobirapp_bot.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.