Мотылек.селестиал.фото.смотреть.селестиал.милый.мотылек. ⌈ #тейк 𝄀 𝅥 @nullscapecf ⌋ ׅ◞
custom 54520596820027387638❤3❤🔥2🍓1custom 54497145869094502861

Channel
@nullscapecf
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
938subscribers
+158 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002901906578 |
|---|---|
| Type | Channel |
| Username | @nullscapecf |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/nullscapecf |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 19:20 | 938 | +23 |
| 3 Sept 2026, 10:59 | 915 | +31 |
| 27 Aug 2026, 09:04 | 884 | +50 |
| 20 Aug 2026, 22:55 | 834 | +24 |
| 14 Aug 2026, 00:15 | 810 | +26 |
| 6 Aug 2026, 18:30 | 784 | +4 |
| 6 Aug 2026, 15:36 | 780 | no change |
| 6 Aug 2026, 12:19 | 780 | first reading |
17 posts held, back to 6 August 2026 — the 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 17 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
129 reactions across 12 posts, in 18 distinct kinds. The most used accounts for 16.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 21 | 16.3% | |
| 👀 | 20 | 15.5% | |
| custom 5452059682002738763 | 18 | 14.0% | |
| custom 5452046088431246690 | 15 | 11.6% | |
| 🍓 | 12 | 9.30% | |
| custom 5449714586909450286 | 8 | 6.20% | |
| custom 5258073597133495528 | 6 | 4.65% | |
| 💘 | 6 | 4.65% | |
| custom 5307849489250294744 | 3 | 2.33% | |
| ❤🔥 | 3 | 2.33% | |
| 💔 | 3 | 2.33% | |
| 🔥 | 3 | 2.33% | |
| custom 5258226781437073211 | 2 | 1.55% | |
| ⚡ | 2 | 1.55% | |
| 🏆 | 2 | 1.55% | |
| 🐳 | 2 | 1.55% | |
| 👻 | 2 | 1.55% | |
| custom 5452038177101487820 | 1 | 0.775% |
Custom emoji. 7 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 12 of the 17 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 129 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 6 August 2026 to 6 August 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.
Мотылек.селестиал.фото.смотреть.селестиал.милый.мотылек. ⌈ #тейк 𝄀 𝅥 @nullscapecf ⌋ ׅ◞
custom 54520596820027387638❤3❤🔥2🍓1custom 54497145869094502861
нулевое пространство ⌈ #тейк 𝄀 𝅥 @nullscapecf ⌋ ׅ◞
custom 54520460884312466909❤1❤🔥1🍓1👀1custom 54520381771014878201
это НЕ вантед ран мы доходим до 25 ПРОСТО ТАК кто не зайдет будет опозорен код 18ew47 у меня 1000000000 ранг и я играю на присонере ⌈ #тейк 𝄀 𝅥 @nullscapecf ⌋ ◞
💔3🍓1custom 54520596820027387631
Чувак настолько отупел от брейнротов, что посидел, поиграл 10 минут, похвалил музыку и вышел. Это всё, на что его хватило. А и игнорирование огромного света👍 Неанон. Ави ⌈ #тейк 𝄀 𝅥 @nullscapecf ⌋ ׅ◞
👀12🍓1
третья попытка на жырвантеда я устала код: 18ew47 - 📄 если че ч типо в эдите с 30 рангом да да и хотя бы типы которые на стандарте 15-20+ сделали пж да ⌈ #тейк 𝄀 𝅥 @nullscapecf ⌋ ◞
🍓1👀1👻1
Прив, попытка номер (???) вб фокс с определенной стратегией мин лвл 10 мин ранк 50+ на хосте 100+ ранк пугратория долько на 8-14 лвле код: 56jevx - 📄 ⌈ #тейк 𝄀 𝅥 @nullscapecf ⌋ ׅ◞
🍓1👀1👻1
о и, хочу показать свои недоэмоджи с опірітіром (+ стикеры) я все еще работаю над ними клянусь 🐧 ⌈ #тейк 𝄀 𝅥 @nullscapecf ⌋ ׅ◞
💘5custom 54520460884312466903custom 54520596820027387632🍓1
камеру вырубай 🐧 ⌈ #тейк 𝄀 𝅥 @nullscapecf ⌋ ׅ◞
custom 54520596820027387637❤3👀3custom 54520460884312466903🍓1
Превет ето колона хумка Пока Неанон Удав ⌈ #тейк 𝄀 𝅥 @nullscapecf ⌋ ׅ◞
custom 54497145869094502867⚡2🏆2❤1🍓1
Продолжаю делать булочек нуллскейп, сейчас сделала дайвера и чарджера. Если хотите кого-то, пишите, я потом сделаю:D неанон Энгель<🔭> ⌈ #тейк 𝄀 𝅥 @nullscapecf ⌋ ׅ◞
❤13🔥2custom 52582267814370732112🍓1
каденс и очень много мартов,,👀👀 (я за ними присматриваю да) ⌈ #тейк 𝄀 𝅥 @nullscapecf ⌋ ◞
custom 52580735971334955286custom 53078494892502947443🍓2🐳2👀2🔥1
🌀 . 💭💭 💭🌟 🌟🌟 💙 Люб𝚞᭙ь Иԋфꫀƙƚ𝙴дα ? 🤩ყꪑαꫀ᭙ь, кყдα ƈкυн𝚢𝚃ь 0️⃣0️⃣ 𝙲вꪮй кꪮнᡶҽԋ𝚃 𝙲 н𝚞𝙼? 🌟🌟🌟 '🍹 🤩1𝚗𝚏3𝚌73𝚍 🌟 Дꪮбᩏσ п𝑜жꪖлσ𝙱𝙰ть 𝙱 🌟 ✨ ✨ 🔤🔤🔤🔤🔤🔤🔤🔤 🔤🔤🔤🔤🔤🔤 💙 〰️ ✨ ✨ ✨ ✨ ✨ Cꊰ + ÐᗩiL𝑌 🐱 💙 . 🌟 - 🐈⬛ ⚪️⚪️ 💾💾 Nᗩvigᗩtion ᴵᴵ ᗰP pꄲst(O+) 𝙱oos𝚃 ᶜᴿ ᴷᴬᴷᴬᴵˢᴬˢˢ
Showing the 12 most recent of 17 posts we hold for @nullscapecf. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@nullscapecf named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“Nullscape confession | cf - daily” (@nullscapecf), 938 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/nullscapecf.
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.