Telegram RegisterThe public register of Telegram
Telegram profile photo for cutierover's basement

Channel

cutierover's basement

@cutierover

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry

56,107subscribers

+1,286 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001269949776
TypeChannel
Username@cutierover
CreatedBetween 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 October 2026
Measurements held50
Confirmed unchanged1 time, most recently 27 October 2026
On Telegramt.me/cutierover

Topic

Gaming — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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.

Growth

53,75159,59156,6717 August 2026 — 54,821 subscribers7 August 2026 — 54,821 subscribers8 August 2026 — 54,857 subscribers9 August 2026 — 54,839 subscribers10 August 2026 — 54,795 subscribers11 August 2026 — 54,867 subscribers12 August 2026 — 54,890 subscribers13 August 2026 — 54,892 subscribers14 August 2026 — 55,028 subscribers16 August 2026 — 55,126 subscribers17 August 2026 — 54,965 subscribers18 August 2026 — 54,912 subscribers19 August 2026 — 54,818 subscribers20 August 2026 — 54,668 subscribers21 August 2026 — 54,653 subscribers23 August 2026 — 54,249 subscribers24 August 2026 — 54,156 subscribers25 August 2026 — 53,841 subscribers26 August 2026 — 53,784 subscribers27 August 2026 — 53,751 subscribers28 August 2026 — 59,591 subscribers29 August 2026 — 59,310 subscribers30 August 2026 — 59,181 subscribers31 August 2026 — 59,111 subscribers2 September 2026 — 59,056 subscribers3 September 2026 — 58,941 subscribers4 September 2026 — 58,900 subscribers8 September 2026 — 58,732 subscribers11 September 2026 — 58,369 subscribers13 September 2026 — 57,753 subscribers14 September 2026 — 57,555 subscribers16 September 2026 — 57,880 subscribers18 September 2026 — 56,180 subscribers25 September 2026 — 58,081 subscribers4 October 2026 — 57,575 subscribers8 October 2026 — 57,142 subscribers13 October 2026 — 56,949 subscribers14 October 2026 — 56,893 subscribers15 October 2026 — 56,819 subscribers16 October 2026 — 56,727 subscribers17 October 2026 — 56,702 subscribers18 October 2026 — 56,678 subscribers19 October 2026 — 56,762 subscribers20 October 2026 — 56,664 subscribers21 October 2026 — 56,538 subscribers22 October 2026 — 56,414 subscribers24 October 2026 — 56,320 subscribers25 October 2026 — 56,245 subscribers26 October 2026 — 56,166 subscribers27 October 2026 — 56,107 subscribers56,1077 August 202627 October 2026
50 measurements spanning 81 days, net +1,286. 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 52,875–60,467 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 50
Measured (UTC)SubscribersChange
27 Oct 2026, 03:3056,107-59
26 Oct 2026, 04:4756,166-79
25 Oct 2026, 03:1156,245-75
24 Oct 2026, 00:0956,320-94
22 Oct 2026, 23:0056,414-124
21 Oct 2026, 18:4156,538-126
20 Oct 2026, 16:5056,664-98
19 Oct 2026, 14:3656,762+84
18 Oct 2026, 16:2756,678-24
17 Oct 2026, 16:4056,702-25
16 Oct 2026, 16:4556,727-92
15 Oct 2026, 14:5956,819-74
14 Oct 2026, 12:4956,893-56
13 Oct 2026, 00:4656,949-193
8 Oct 2026, 14:1757,142-433
4 Oct 2026, 04:1957,575-506
25 Sept 2026, 11:1558,081+1,901
18 Sept 2026, 20:3956,180-1,700
16 Sept 2026, 13:5657,880+325
14 Sept 2026, 17:4057,555first reading

Engagement

174 posts held, back to 28 July 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 181 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
20.5%
avg views ÷ 56,107 subscribers
Avg views / post
11,500
61 posts measured
Reaction rate
2.50%
reactions ÷ views · ER floor
Posts in window
61
of 174 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 26 October 2026
Posts held174 (28 July 2026 – 26 October 2026)
Views total702,110
Reactions total17,573
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken26 Oct 2026, 23:52 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

Video runtime
2m 39s
Average length
53s

Measured directly from 3 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

51,474 reactions across 174 posts, in 2 distinct kinds. The most used accounts for 74.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 535057563493232050038,36974.5%
custom 519726759334538532713,10525.5%

Custom emoji. Every row above is a 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 174 of the 174 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 51,474 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 174 most recent posts we hold, published 28 July 2026 to 26 October 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.

Telegram Stars

Stars received
277
across the posts below
Posts paid on
51
of 174 we hold a reading for · 29%
Most on one post
110
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @cutierover. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 174 most recent posts we hold for this entry, published 28 July 2026 to 26 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

26 Oct 2026, 11:37 UTC≈5,320 views140 reactionsread 26 October 2026
Photo

😀 стрим вечером, поиграем в нашумевшую игру “Flipping is Hard” а после пойдем на boosty смотреть «Начало»

custom 5350575634932320500113custom 519726759334538532727

25 Oct 2026, 15:40 UTC≈7,490 views275 reactionsread 26 October 2026
Photo

прифотошопили вещи в карманы ппц

custom 5350575634932320500227custom 519726759334538532748

25 Oct 2026, 11:33 UTC≈7,770 views167 reactionsread 26 October 2026
Photo

📞 стрим вечером, сегодня я попробую себя в роле скамера в игре "Scam With Your Friends" так же пройдет 2 аукциона, первый за донат на "Паракорд-нож | Волны" и другой за баллы "Нож Боуи | Черный глянец" 💪 не забывайте про розыгрыш для рефов (без депа)

custom 5350575634932320500144custom 519726759334538532723

25 Oct 2026, 08:43 UTC≈8,070 views313 reactionsread 26 October 2026
Photo

подрабатываю, и что?

custom 5350575634932320500270custom 519726759334538532743

24 Oct 2026, 20:26 UTC≈8,460 views295 reactionsread 26 October 2026

мне разрешили завести домашнего питомца, я счастлива, завтра на твиче расскажу как так вышло, там вообще абсурд.. 👀

custom 5350575634932320500243custom 519726759334538532752

24 Oct 2026, 17:53 UTC≈8,540 views128 reactionsread 26 October 2026
Photo

стрим на бусти онлайн, чуть поговорим и пойдем начинать 3 сезон осд (есть бесплатная пробная подписка) 🌸 посмотреть запись: https://boosty.to/cutierover

custom 5350575634932320500113custom 519726759334538532715

24 Oct 2026, 16:20 UTC≈8,370 views131 reactionsread 26 October 2026

к 21:00 запущу +- 😲

custom 5350575634932320500113custom 519726759334538532718

24 Oct 2026, 14:49 UTC≈8,270 views188 reactionsread 26 October 2026
Photo

хотите сегодня начнем 3 сезон пару серий "Очень странные дела" на boosty? должен был быть сегодня на твиче, но мой завоз пришел бракованным, ну ниче

custom 5350575634932320500160custom 519726759334538532728

24 Oct 2026, 08:58 UTC≈8,340 views336 reactionsread 26 October 2026
Photo

вчера прикольно посидели

custom 5350575634932320500278custom 519726759334538532758

23 Oct 2026, 19:25 UTC≈8,740 views218 reactionsread 26 October 2026
Photo

один шиномонтажник сказал, что шины хорошие, можно спокойно ездить, другой же сказал, что нужно менять и кому верить? 🥴 сегодня без стрима, еду на вечеринку какую-то позвали там типа круто должно быть

custom 5350575634932320500185custom 519726759334538532733

23 Oct 2026, 15:01 UTC≈8,980 views286 reactionsread 26 October 2026
Photo

забрала 😈

custom 5197267593345385327236custom 535057563493232050050

23 Oct 2026, 11:40 UTC≈9,200 views388 reactions1 Starread 26 October 2026
Photo

как вам свитер?

custom 5350575634932320500319custom 519726759334538532769

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts edited after publishing

@cutierover edited 7 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
31 August 2026
Most recent edit
26 October 2026

Forward network

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.

Mentions

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

“cutierover's basement” (@cutierover), 56,107 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/cutierover.

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.