Telegram RegisterThe public register of Telegram

Channel

CHROME ❇︎ TEARS

@CHR8ME

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

168subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002896021117
TypeChannel
Username@CHR8ME
Descriptionㅤ 2000s AND ㅤ ㅤ EMOTIONALLY ㅤ ㅤ ICONIC: ㅤ @CHROMETEARSBOT ㅤ @CRYINCHROME 🖨️
Created13 July 2025measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/CHR8ME

Growth

1687 August 2026 — 168 subscribers8 August 2026 — 168 subscribers7 August 20268 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 167–169 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 15:31168no change
7 Aug 2026, 03:02168first reading

Engagement

15 posts held, back to 13 July 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
19.8%
avg views ÷ 168 subscribers
Avg views / post
33.3
3 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
3
of 15 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 27 July 2026
Posts held15 (13 July 202527 July 2026)
Views total100
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 15:31 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
4
Videos
2
Links
3

Lifetime counters from Telegram’s own channel header, read 8 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.

Video runtime
2m 38s
Average length
1m 19s

Measured directly from 2 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.

Recent posts

27 Jul 2026, 09:49 UTC24 viewsread 8 August 2026

TRANSMISSION: UNSTABLE FILE FOUND ⠀⠀⠀⠀ ⠀⠀⠀⠀STORED IN CHROME ❇︎ NAME: CHROME TEARS / TYPE: emotional debris / log / residual.mp3 / STATUS: SEEKING CONNECTIONS? ⠀⠀⠀This channel is now syncing with⠀⠀⠀ subs-for-subs. Send your coordinates⠀⠀⠀ to @ HOLD ⠀⠀⠀🧷

2 Jan 2026, 13:57 UTC570 viewsread 8 August 2026

We are putting SFS on hold for a bit yaaa. To everyone who already submitted through our bot, we'll get back to you soon

20 Dec 2025, 15:03 UTC765 viewsread 8 August 2026
Photo

SIGNAL: CHROME TEARS | TEENAGE FREQUENCY (Chrome Tears frequency stabilizing, laughter detected, worries minimized) CHROME TEARS: FUN > FEAR. TRANSMISSION ONGOING.

16 Dec 2025, 16:33 UTC859 viewsread 8 August 2026
Photo

TRANSMISSION INITIATED: [001] CHROME TEARS x DEFTONES DETECTED | STATUS: SYNCHRONIZING… Play tear_stream.mp3 at your own risk: heart reboot protocol active. Coordinates accepted via www.CHROMETEARS.com & keep your system dark, keep your style chrome. TRANSMISSION CLOSED: [002] SIGNALS FADING. RESIDUAL OF CHROME TEARS & CHERRY WAVES STORED IN THE BLACK DOMAIN. HEART REBOOT COMPLETE: @slebknot @glazte @yioonseo @pIeset

8 Aug 2025, 17:32 UTC933 viewsread 8 August 2026
Photo

⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀ CHROMETEARS.COM ⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀

8 Aug 2025, 17:32 UTC993 viewsread 8 August 2026

They call them CHROME / TEARS: not water, but fragments of alloyed grief, spilling in slow arcs through static air, each one refracting a spectrum the eye cannot name. They run cold, almost mechanical, yet somewhere in their descent is the pulse of something unspoken, a current that hums in a language only the heart deciphers. Some say they are relics, residue of nights stretched too thin, of voices that once fit p

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

Citation-graph rank

Citation-graph rank — 1,045,682 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

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.

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

“CHROME ❇︎ TEARS” (@CHR8ME), 168 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/CHR8ME.

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.