Telegram RegisterThe public register of Telegram
Telegram profile photo for xxtrahot

Channel

xxtrahot

@queen_shika123

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

176subscribers

-57 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1003884298508
TypeChannel
Username@queen_shika123
CreatedBetween 1 February 2026 and 7 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live17 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/queen_shika123

Topic

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 24 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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

176233204.514 August 2026 — 233 subscribers14 August 2026 — 233 subscribers22 August 2026 — 215 subscribers29 August 2026 — 206 subscribers8 September 2026 — 184 subscribers17 September 2026 — 176 subscribers14 August 202617 September 2026
6 measurements spanning 34 days, net -57. 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–242 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 03:20176-8
8 Sept 2026, 13:00184-22
29 Aug 2026, 08:04206-9
22 Aug 2026, 11:07215-18
14 Aug 2026, 21:38233no change
14 Aug 2026, 10:17233first reading

Engagement

17 posts held, back to 7 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 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 12 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
3m 46s
Average length
45s

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

12 Aug 2026, 15:26 UTC195 viewsread 14 August 2026

halo, ini shika. aku mau minta maaf yang sebesar-besarnya karena tindakan aku yang gegabah dan fatal yang berujung merugikan mirz dan reynar. aku minta maaf juga karena jadi salah satu orang yang bikin masalah ini jadi rame dan makin kesebar. aku seharusnya bisa bertindak lebih bijak dalam menyaring informasi, terlebih lagi aku dan mirz berada dalam satu lingkup yang sama. ngga ada pembelaan sama sekali dari aku kare…

10 Aug 2026, 01:06 UTC171 viewsread 14 August 2026
Forwarded from @made2blessVideo

Video, posted without a caption

7 Aug 2026, 17:05 UTC263 viewsread 14 August 2026
Forwarded from @nuavesVideo

Video, posted without a caption

16 Jul 2026, 17:25 UTC577 viewsread 14 August 2026
Forwarded from @tatjaslimestoreVideo

Video, posted without a caption

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

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

“xxtrahot” (@queen_shika123), 176 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/queen_shika123.

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.