Telegram RegisterThe public register of Telegram
Telegram profile photo for Зарубежные карты | SkyZit 🌙

Bot

Зарубежные карты | SkyZit 🌙

@skyzit_bot

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

10,555monthly users

-3,881 since we began measuring on 6 August 2026

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

Register entry

Telegram ID8128788848
TypeBot
Username@skyzit_bot
First recorded20 August 2026
Last confirmed live8 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/skyzit_bot

Growth

10,55514,43612,495.56 August 2026 — 14,436 monthly users8 August 2026 — 13,652 monthly users11 August 2026 — 13,142 monthly users13 August 2026 — 13,602 monthly users14 August 2026 — 13,470 monthly users17 August 2026 — 12,382 monthly users19 August 2026 — 12,294 monthly users20 August 2026 — 12,294 monthly users22 August 2026 — 12,467 monthly users25 August 2026 — 11,560 monthly users28 August 2026 — 11,290 monthly users30 August 2026 — 11,948 monthly users1 September 2026 — 11,913 monthly users3 September 2026 — 11,177 monthly users8 September 2026 — 10,555 monthly users6 August 20268 September 2026
15 measurements spanning 34 days, net -3,881. 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 9,973–15,018 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
8 Sept 2026, 14:4010,555-622
3 Sept 2026, 09:3711,177-736
1 Sept 2026, 02:3411,913-35
30 Aug 2026, 02:0411,948+658
28 Aug 2026, 03:2311,290-270
25 Aug 2026, 05:4711,560-907
22 Aug 2026, 11:2712,467+173
20 Aug 2026, 20:1112,294no change
19 Aug 2026, 19:0512,294-88
17 Aug 2026, 13:5712,382-1,088
14 Aug 2026, 16:0513,470-132
13 Aug 2026, 03:3413,602+460
11 Aug 2026, 01:1813,142-510
8 Aug 2026, 21:1013,652-784
6 Aug 2026, 00:5314,436first 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.

Mentions

Named by 5 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 8 September 2026 — this entry's latest reading, not the date you are reading this.

“Зарубежные карты | SkyZit 🌙” (@skyzit_bot), 10,555 monthly users as measured 8 September 2026. Telegram Register, tgregister.com/channel/skyzit_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.