Telegram RegisterThe public register of Telegram
Telegram profile photo for NO!SEBLEED rec.

Channel

NO!SEBLEED rec.

@noisebleedrec

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

176subscribers

+8 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-1003645764451
TypeChannel
Username@noisebleedrec
CreatedBetween 1 December 2025 and 24 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live19 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/noisebleedrec

Growth

1681761728 August 2026 — 168 subscribers8 August 2026 — 168 subscribers9 August 2026 — 169 subscribers16 August 2026 — 170 subscribers24 August 2026 — 172 subscribers10 September 2026 — 175 subscribers19 September 2026 — 176 subscribers8 August 202619 September 2026
7 measurements spanning 42 days, net +8. 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–177 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 08:38176+1
10 Sept 2026, 09:57175+3
24 Aug 2026, 11:54172+2
16 Aug 2026, 08:12170+1
9 Aug 2026, 02:01169+1
8 Aug 2026, 15:31168no change
8 Aug 2026, 06:33168first reading

Engagement

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

Reaction mix

204 reactions across 11 posts, in 6 distinct kinds. The most used accounts for 77.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
15777.0%
🔥2411.8%
❤‍🔥104.90%
👍73.43%
😍31.47%
🥰31.47%

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 11 of the 11 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 204 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 24 April 2026 to 7 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

7 Aug 2026, 17:27 UTC44 views9 reactionsread 8 August 2026
Forwarded from @mrmsclPhoto

21грам – київський нінтендокор, аналогів якому в країні немає. 8бітні сінти, нищівні барабани, голос вокаліста зривається. Це як вколоти кока-колу по вені після того, як тиждень блукав пустелею без води. South!West!District! – скрімо та емо-вайленс гурт-симбіоз між Києвом та Черкасами, який передає усю атмосферу однойменного району через сирий крик, гучний фідбек гітар та різкими змінами темпу, наче американські гір

6🔥2👍1

26 Jul 2026, 17:20 UTC649 views25 reactionsread 8 August 2026
Photo

SUMMER FALL FEST 18/19.07

18🔥4😍2👍1

19 Jul 2026, 19:56 UTC552 views31 reactionsread 8 August 2026

Народ дякуємо за фест! Ви найкращі! Дякуємо також гуртам які долучилися і приїхали, без вас цього всього не сталося би!!!!! Фото і відео з івенту по наявності в коментарі!

23❤‍🔥7🔥1

18 Jul 2026, 19:47 UTC359 views25 reactionsread 8 August 2026

Всім присутнім сьогодні дуже дякуємо було дуже круто! Відео/фото по наявності в скидайте коментарі!

20🥰3🔥2

15 Jul 2026, 11:19 UTC403 views13 reactionsread 8 August 2026

https://www.youtube.com/watch?v=obd37qf1NyA

9🔥3😍1

2 Jul 2026, 22:43 UTC808 views12 reactionsread 8 August 2026
Photo

juzowillbefine x Сьогодні Минуле - гераскофобiя спотіфай | телеграм | інстаграм | ютуб музика | сьогодні минуле

10👍1🔥1

29 Jun 2026, 14:00 UTC≈4,300 views19 reactionsread 8 August 2026
Photo

SUMMER FALL 18/19.07 DAY 1 спогади _неймлес 2020summer squallofyoursilince ih8project DAY 2 angelinabelfry perplexité South!west!District! Please be nice 21грам РВРБ вул. нижньоюрківська 31 За квитками СЮДИ По убд вхід безкоштовно квитки передпродаж на один день 500, на два дні 800 передпродаж подвійних квитків на один день 650, на два дні 1200 до 06.07 квитки на вході на один день 600, на два дні 1000 афіша м

14🔥4👍1

21 May 2026, 23:44 UTC≈1,320 views13 reactionsread 8 August 2026
File

File, posted without a caption

11❤‍🔥1🔥1

21 May 2026, 23:44 UTC≈1,450 views18 reactionsread 8 August 2026
Photo

juzowillbefine - мертва весна спотіфай | телеграм | інстаграм

15❤‍🔥2🔥1

26 Apr 2026, 19:24 UTC744 views25 reactionsread 8 August 2026

Всім присутнім сьогодні дякуємо! Відео/фото в скидайте коментарі

21🔥3👍1

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

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

“NO!SEBLEED rec.” (@noisebleedrec), 176 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/noisebleedrec.

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.