Telegram RegisterThe public register of Telegram
Telegram profile photo for OpenDataUA

Bot

OpenDataUA

@OpenDataUABot

Verified by Telegram

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

118,922monthly users

-19,436 since we began measuring on 6 August 2026

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

Register entry

Telegram ID215115043
TypeBot
Username@OpenDataUABot
First recorded9 August 2026
Last confirmed live16 November 2026
Measurements held50
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/OpenDataUABot

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 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 the other topics.

Growth

118,922140,427129,674.56 August 2026 — 138,358 monthly users7 August 2026 — 140,427 monthly users9 August 2026 — 140,427 monthly users10 August 2026 — 137,187 monthly users11 August 2026 — 135,822 monthly users12 August 2026 — 136,034 monthly users14 August 2026 — 137,583 monthly users17 August 2026 — 129,291 monthly users19 August 2026 — 129,492 monthly users20 August 2026 — 130,039 monthly users21 August 2026 — 131,303 monthly users23 August 2026 — 131,686 monthly users24 August 2026 — 129,282 monthly users25 August 2026 — 127,674 monthly users26 August 2026 — 128,295 monthly users28 August 2026 — 130,657 monthly users30 August 2026 — 128,101 monthly users31 August 2026 — 126,728 monthly users2 September 2026 — 127,180 monthly users4 September 2026 — 129,880 monthly users7 September 2026 — 125,988 monthly users10 September 2026 — 126,359 monthly users12 September 2026 — 128,585 monthly users14 September 2026 — 125,213 monthly users15 September 2026 — 125,479 monthly users18 September 2026 — 127,379 monthly users29 September 2026 — 123,824 monthly users5 October 2026 — 125,320 monthly users9 October 2026 — 126,980 monthly users13 October 2026 — 123,193 monthly users14 October 2026 — 123,898 monthly users17 October 2026 — 126,162 monthly users17 October 2026 — 125,747 monthly users18 October 2026 — 123,570 monthly users21 October 2026 — 122,377 monthly users22 October 2026 — 122,621 monthly users23 October 2026 — 123,764 monthly users24 October 2026 — 124,634 monthly users26 October 2026 — 122,696 monthly users27 October 2026 — 121,477 monthly users29 October 2026 — 123,613 monthly users31 October 2026 — 124,320 monthly users1 November 2026 — 121,887 monthly users3 November 2026 — 120,339 monthly users4 November 2026 — 120,569 monthly users5 November 2026 — 121,638 monthly users6 November 2026 — 122,483 monthly users8 November 2026 — 121,928 monthly users9 November 2026 — 119,136 monthly users16 November 2026 — 118,922 monthly users6 August 202616 November 2026
50 measurements spanning 102 days, net -19,436. 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 115,696–143,653 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 50
Measured (UTC)Monthly usersChange
16 Nov 2026, 13:09118,922-214
9 Nov 2026, 12:10119,136-2,792
8 Nov 2026, 07:16121,928-555
6 Nov 2026, 23:56122,483+845
5 Nov 2026, 20:42121,638+1,069
4 Nov 2026, 22:45120,569+230
3 Nov 2026, 19:19120,339-1,548
1 Nov 2026, 15:16121,887-2,433
31 Oct 2026, 17:35124,320+707
29 Oct 2026, 13:57123,613+2,136
27 Oct 2026, 12:49121,477-1,219
26 Oct 2026, 10:15122,696-1,938
24 Oct 2026, 11:28124,634+870
23 Oct 2026, 09:34123,764+1,143
22 Oct 2026, 09:50122,621+244
21 Oct 2026, 04:30122,377-1,193
18 Oct 2026, 22:17123,570-2,177
17 Oct 2026, 23:09125,747-415
17 Oct 2026, 00:39126,162+2,264
14 Oct 2026, 23:34123,898first 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 13 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.

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Wikipedia

One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.

Opendatabot (uk.wikipedia.org)
“…Посилання == * [https://t.me/OpenDataUABot Опендатабот в Телеграмі] {{Webarchive|url=https://web.archive.org/web/20201204092446/https://t.me/OpenDataUABot |date=4…”
read 1 November 2026

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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“OpenDataUA” (@OpenDataUABot), 118,922 monthly users as measured 16 November 2026. Telegram Register, tgregister.com/channel/OpenDataUABot.

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.