Telegram RegisterThe public register of Telegram
Telegram profile photo for Chrollo's Cart

Channel

Chrollo's Cart

@chrolloscart

On this record: Topic · Growth · Engagement · Posts · Cite this entry

15subscribers

+12 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-1004497929686
TypeChannel
Username@chrolloscart
Created27 June 2026 — measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live13 November 2026
Measurements held5
Confirmed unchanged10 times, most recently 13 November 2026
On Telegramt.me/chrolloscart

Topic

Software piracy — 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 1 October 2026 and assigned it the closest of 31 fixed categories, at 75% 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 the other topics.

Growth

31597 August 2026 — 3 subscribers13 August 2026 — 3 subscribers14 August 2026 — 5 subscribers21 August 2026 — 12 subscribers27 August 2026 — 15 subscribers7 August 202627 August 2026
5 measurements spanning 20 days, net +12. 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 1–17 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 14:1215+3
21 Aug 2026, 04:1412+7
14 Aug 2026, 18:085+2
13 Aug 2026, 15:323no change
7 Aug 2026, 19:413first reading

Engagement

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

Recent posts

6 Jul 2026, 09:58 UTC246 viewsread 13 August 2026

Hbo Max Solo Acc(1 month)- 40 Hbo Max Solo Acc (3 months)-80 Prime Video Solo Acc (1mth) - 40 Prime Video Solo Acc (6mths) - 100 Apple TV Solo Account - 40 Viu 1 yr Solo Account - 80 Iwant 1yr Solo Account - 80 Spotify fam via inv - 50 Spotify 3 months provided acc - 70 @Chadwicked

27 Jun 2026, 14:23 UTC37 viewsread 13 August 2026

Lfb/rs: HBO Max 1 Month Solo Account Prime Video 1 Month Solo Account Grammarly Pro 1 Month @Chadwicked

Showing the 6 most recent of 6 posts we hold for @chrolloscart. 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.

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

“Chrollo's Cart” (@chrolloscart), 15 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/chrolloscart.

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.