Telegram RegisterThe public register of Telegram
Telegram profile photo for Crimson Fruits(') Channel (Odio gli USA)

Channel

Crimson Fruits(') Channel (Odio gli USA)

@CanaleNoioso

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

29subscribers

+3 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-1001120638252
TypeChannel
Username@CanaleNoioso
Created23 August 2017measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded11 August 2026
Last confirmed live23 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/CanaleNoioso

Growth

2630287 August 2026 — 26 subscribers11 August 2026 — 26 subscribers15 August 2026 — 30 subscribers23 August 2026 — 29 subscribers297 August 202623 August 2026
4 measurements spanning 15 days, net +3. 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 25–31 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 05:4229-1
15 Aug 2026, 01:0330+4
11 Aug 2026, 09:0226no change
7 Aug 2026, 19:4826first reading

Engagement

20 posts held, back to 18 June 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 4 September 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

16 Aug 2025, 12:05 UTC63 viewsread 11 August 2026
Photo

Bruh, davvero ora YouTube ti mette gli ad pure in basso quando non sta venendo più riprodotto? This shit's so ass

Signed CriMoonSon

15 Aug 2025, 13:59 UTCviews —

Crimson Fruits(') Channel (Odio gli USA) pinned «https://fightchatcontrol.eu/#contact-tool»

31 Jul 2025, 13:27 UTC59 viewsread 11 August 2026

NUOVO OCTOPATH, GODOOOOOOOOOOOOOOOOOOOOOOOOOOOO

Signed CriMoonSon

31 Jul 2025, 13:02 UTC55 viewsread 11 August 2026

Damn, sta andando proprio bene come serie spin-off

Signed CriMoonSon

31 Jul 2025, 12:51 UTC53 viewsread 11 August 2026

Io tra 9 minuti https://youtu.be/pct1uEhAqBQ?feature=shared

Signed CriMoonSon

27 Jul 2025, 12:30 UTC44 viewsread 11 August 2026

What the hell https://www.eastjournal.net/archives/143936

Signed CriMoonSon

17 Jul 2025, 06:37 UTC42 viewsread 11 August 2026
Photo

???????????????????????????????????????

Signed CriMoonSon

Showing the 12 most recent of 20 posts we hold for @CanaleNoioso. 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 23 August 2026 — this entry's latest reading, not the date you are reading this.

“Crimson Fruits(') Channel (Odio gli USA)” (@CanaleNoioso), 29 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/CanaleNoioso.

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.