Telegram RegisterThe public register of Telegram

Channel

re.BASTET cdt

@bastetuska

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

187subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001922991298
TypeChannel
Username@bastetuska
Description🌟 K-POP COVER DANCE TEAM FROM KEMEROVO, RUSSIA 🌟 YT: https://youtube.com/@re.bastet7551
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/bastetuska

Growth

1878 Aug 2026, 09:31 — 187 subscribers8 Aug 2026, 12:05 — 187 subscribers8 Aug 2026, 09:318 Aug 2026, 12:05
2 measurements taken within a single day. 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 186–188 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 12:05187no change
8 Aug 2026, 09:31187first reading

Engagement

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

ERR · 30 days
202.6%
avg views ÷ 187 subscribers
Avg views / post
379
8 posts measured
Reaction rate
8.05%
reactions ÷ views · ER floor
Posts in window
8
of 9 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 3 August 2026
Posts held9 (14 July 20263 August 2026)
Views total3,031
Reactions total244
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 12:05 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
447
Videos
104
Links
101

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
51s
Average length
17s

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

288 reactions across 9 posts, in 11 distinct kinds. The most used accounts for 22.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54116362787414463326622.9%
custom 52424076094320252436321.9%
5519.1%
custom 52109791991284484764415.3%
🔥186.25%
💋124.17%
💘82.78%
🦄82.78%
🍓72.43%
❤‍🔥62.08%
🥴10.347%

Custom emoji. 3 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 areTelegram’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 9 of the 9 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 288reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 9 most recent posts we hold, published 14 July 2026 to 3 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.

Recent posts

3 Aug 2026, 15:48 UTC344 views34 reactionsread 8 August 2026
Video

💬💬💬

10custom 52424076094320252437custom 54116362787414463327custom 52109791991284484764🦄2❤‍🔥1🍓1💋1

1 Aug 2026, 16:09 UTC273 views26 reactionsread 8 August 2026

Увидимся на k-core в номинации OLD💥💪🏻

custom 52424076094320252437custom 54116362787414463326custom 521097919912844847643💋2🔥2🍓1💘1

1 Aug 2026, 16:09 UTC51 views24 reactionsread 8 August 2026
Forwarded from @kcorefestPhoto

Мы готовы объявить результаты отбора заявок! Номинации и участники на k-core fest. 2026 Сопроводительные письма будут отправлены Вам на почту (в пн) С нетерпением ждем вас на фестивале! С любовью, команда k-core 💥

6custom 52109791991284484764💋3🔥3custom 54116362787414463323💘2custom 52424076094320252432🍓1

25 Jul 2026, 15:45 UTC312 views13 reactionsread 8 August 2026

Ещё один человек!!

6custom 52109791991284484764custom 52424076094320252433

24 Jul 2026, 16:26 UTC433 views27 reactionsread 8 August 2026

💬Ищем людей на подтанцовку в проект GIRLSET — 'CHAT' Требования: • ответственность • скилл средний и выше • быстрая обучаемость • платежеспособность Также мы попросим видео с кусочком любой хореографии в вашем исполнении!! Писать: @Elisafiz

custom 54116362787414463329custom 52109791991284484768custom 524240760943202524382

18 Jul 2026, 15:36 UTC650 views41 reactionsread 8 August 2026
Video

🫂🤍

custom 524240760943202524316custom 541163627874144633210custom 521097919912844847663❤‍🔥1🍓1💋1💘1

15 Jul 2026, 09:25 UTC594 views34 reactionsread 8 August 2026

Come gimme dat🐚 Новый кавер на I-DLE — 'GIMME DAT LOVE' уже на канале!! Не забудьте поддержать лайком и написать комментарий🤍

custom 52424076094320252439custom 54116362787414463329custom 52109791991284484765💋3❤‍🔥2🔥21🍓1

15 Jul 2026, 04:02 UTC374 views45 reactionsread 8 August 2026
Photo

'GIMME DAT LOVE' TEASER PHOTOS🐚🪸 ▫️Yoshi as Soyeon ▫️Ririii as Miyeon ▫️Razji as Minnie ▫️Lixy as Yuqi ▫️Elisafiz as Shuhua Не забудьте поставить реакцию!!

15custom 52424076094320252439custom 54116362787414463328custom 52109791991284484766🔥2❤‍🔥1💋1💘1

14 Jul 2026, 03:34 UTC352 views44 reactionsread 8 August 2026
Photo

☀️🐚🌴🐬

custom 5411636278741446332149🔥8🦄3custom 52109791991284484763🍓2custom 52424076094320252432❤‍🔥1

Showing the 9 most recent of 9 posts we hold for @bastetuska. 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 — 410,870 of 1,169,250entries 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.

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

“re.BASTET cdt” (@bastetuska), 187 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/bastetuska.

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.