Telegram RegisterThe public register of Telegram
Telegram profile photo for BlackSnow

Channel

BlackSnow

@Blacksnow_f

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

118subscribers

-7 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002422756493
TypeChannel
Username@Blacksnow_f
Created28 January 2025measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live31 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/Blacksnow_f

Growth

1181261226 August 2026 — 125 subscribers9 August 2026 — 125 subscribers15 August 2026 — 126 subscribers23 August 2026 — 122 subscribers31 August 2026 — 118 subscribers6 August 202631 August 2026
5 measurements spanning 24 days, net -7. 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 117–127 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 02:42118-4
23 Aug 2026, 03:41122-4
15 Aug 2026, 20:18126+1
9 Aug 2026, 02:32125no change
6 Aug 2026, 23:03125first reading

Engagement

7 posts held, back to 28 January 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 7 posts for this entry, the most recent from 18 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
48s
Average length
12s

Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

28 reactions across 6 posts, in 6 distinct kinds. The most used accounts for 35.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1035.7%
❤‍🔥932.1%
🔥517.9%
🍌27.14%
👍13.57%
🥰13.57%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 6 of the 7 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 28 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 28 January 2025 to 18 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

18 Jul 2026, 16:41 UTC109 views9 reactionsread 9 August 2026
Video

> День/ночь, встретил ещё одну версию Мику, но куда она катит эту тележку с чиби?... < Извиняюсь за долгое отсутствие постов, было лень... Спасибо за помощь с фоном Чёрным Меткам #Аним #Мику

7👍1🥰1

30 Jun 2026, 10:46 UTC96 views3 reactionsread 9 August 2026
Forwarded from @YinYanTeamPhoto

🎉 РОЗЫГРЫШ от Yin&Yang Team 🎉 Наша команда Yin&Yang Team совместно со спонсором розыгрыша — уважаемым @messur — запускает розыгрыш трёх фигурок! 🏆 Призы: 🥇 1 место — фигурка, где Мику сидит на дереве. 🥈 2 место — фигурка, где Мику сидит. 🥉 3 место — фигурка, где Мику в повседневной одежде. 📋 Условия участия: Подписаться на Telegram-каналы: • Yin&Yang Team — @YinYanTeam • Телеграмм-канал заведующего медиа Narkeno

3

24 May 2026, 19:31 UTC281 views5 reactionsread 9 August 2026
Video

> День/ночь, захотел взять гитару в мире «Бесконечного лета», а именно во Вселенной 35 градусов, но похоже, я зашёл очень не вовремя... < Решил изучить новую программу для анимации, и эта моя первая работа в ней. #Аним #35 #БЛ

❤‍🔥4🔥1

17 May 2026, 10:17 UTC230 views3 reactionsread 9 August 2026
Video

> День/ночь, на улице жарко, хочется в холодные края. Как насчёт отправиться в мир «Выбери меня»? Там точно есть холодный этаж, А Хан нас будет сопровождать. < #Аним #Хан #ВыбериМеня

🔥2❤‍🔥1

16 May 2026, 12:15 UTC140 views4 reactionsread 9 August 2026
Video

> День/Ночь, не желаете ли для начала, понежиться в кроватке? < В будущем часто будем останавливаться на этой остановке #Аним #PA15

❤‍🔥4

14 May 2026, 10:01 UTC715 views4 reactionsread 9 August 2026
Video

День/Ночь, друзья, не желаете прокатиться вместе со мной по разным мирам? #БЛ #Аним

🍌2🔥2

Showing the 7 most recent of 7 posts we hold for @Blacksnow_f. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

“BlackSnow” (@Blacksnow_f), 118 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/Blacksnow_f.

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.