Telegram RegisterThe public register of Telegram
Telegram profile photo for 🤪

Channel

🤪

@spillcarmenverses

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

4subscribers

+0 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1003842882011
TypeChannel
Username@spillcarmenverses
CreatedBetween 1 February 2026 and 15 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live11 September 2026
Measurements held2
On Telegramt.me/spillcarmenverses

Growth

411 August 2026 — 4 subscribers13 August 2026 — 4 subscribers11 August 202613 August 2026
2 measurements spanning 2 days. 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 3–5 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 10:024no change
11 Aug 2026, 10:194first reading

Engagement

20 posts held, back to 15 June 2026the 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 20 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
6
Videos
1
Links
7

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

9 Aug 2026, 12:48 UTC58 viewsread 13 August 2026

membernya ditampung carmodice ternyata ya ownernya juga bermasalah bukan.

9 Aug 2026, 03:40 UTC92 viewsread 13 August 2026

nantikan proofnya ya soalnya ada beberapa yang newlife tapi masih bawa-bawa orang diakun lama loh.

9 Aug 2026, 03:39 UTC109 viewsread 13 August 2026

hati-hati aja @carmodice @dulcearmeen @carminous @carmerie @lotusrmen nanti kemasukan member carmenverses yang lain loh nanti dorm kalian jadi jelek gara-gara kemasukan orang orang yang suka curang sfs.

17 Jun 2026, 14:07 UTC≈1,440 viewsread 13 August 2026
Forwarded from @AnoMessBot

‌ ‌‌‌ ‌ Nanggung banget malah rest Carmenverses, kenapa gk sekalian DISBAND aja? Nanggung udah downfall gk bisa diperbaiki.

17 Jun 2026, 11:53 UTC≈1,450 viewsread 13 August 2026
Forwarded from @AnoMessBot

‌ ‌‌‌ ‌ https://t.me/spillcarmenverses/22 selain dari curang sfs, jangan lupain kasus ishay yg ini min. yg ini udah fatal banget.

17 Jun 2026, 11:52 UTC≈1,360 viewsread 13 August 2026
Forwarded from @AnoMessBot

‌ ‌‌‌ ‌ ke cc gua aja minta nambah 3 acc tapi kagak ada feedback padahal mintanya cuma 3

17 Jun 2026, 11:49 UTC≈1,340 viewsread 13 August 2026
Forwarded from @AnoMessBot

‌ ‌‌‌ ‌ https://t.me/spillcarmenverses/67 sepakat. semuanya ikuti gerakan unsubs carmenverses yuk, apa yg diharepin dari cc curang sfs ini?

17 Jun 2026, 04:01 UTC≈1,250 viewsread 13 August 2026

kan gw dah kasih tau ishay ishay, lu sih bebal jadinya ketahuan kan.

Showing the 12 most recent of 20 posts we hold for @spillcarmenverses. 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 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“🤪” (@spillcarmenverses), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/spillcarmenverses.

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.