Telegram RegisterThe public register of Telegram

Channel

Lingering Pain

@Lingering_Pain

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry

185subscribers

+0 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-1002539603935
TypeChannel
Username@Lingering_Pain
DescriptionМенеджер: @LingPainPop
CreatedBetween 1 March 2025 and 31 July 2025— 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/Lingering_Pain

Growth

1857 Aug 2026, 15:53 — 185 subscribers8 Aug 2026, 12:16 — 185 subscribers7 Aug 2026, 15:538 Aug 2026, 12:16
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 184–186 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 12:16185no change
7 Aug 2026, 15:53185first reading

Engagement

19 posts held, back to 27 August 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 19 posts for this entry, the most recent from 18 October 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
35
Videos
22
Links
18

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
59s
Average length
20s

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

346 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 28.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52197880396135946099728.0%
custom 52223892994413195186619.1%
custom 53778556308139643615014.5%
custom 54541128309890257524813.9%
custom 59990223841688341814813.9%
custom 5404529538090672257308.67%
custom 522196825520735629372.02%

Custom emoji. Every row above is a 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 19 of the 19 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 346reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 27 August 2025 to 18 October 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
21
across the posts below
Posts paid on
7
of 19 we hold a reading for · 37%
Most on one post
6
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Lingering_Pain. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 19 most recent posts we hold for this entry, published 27 August 2025 to 18 October 2025. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

18 Oct 2025, 21:06 UTC≈1,830 views10 reactionsread 8 August 2026

https://band.link/TVZhv Слушаем, радуемся. Трек реально разьеб Mix by - yukkayo Обложка - THE DARIS

custom 54541128309890257525custom 52197880396135946093custom 53778556308139643612

18 Oct 2025, 11:09 UTC≈1,460 views11 reactionsread 8 August 2026

Этой ночью🤫

custom 52197880396135946094custom 54541128309890257523custom 52223892994413195182custom 53778556308139643612

15 Oct 2025, 13:00 UTC≈1,260 views12 reactionsread 8 August 2026

Как ваши дела вообще, рассказывайте!!

custom 54045295380906722575custom 52197880396135946093custom 52223892994413195183custom 53778556308139643611

15 Oct 2025, 11:43 UTC≈1,240 views18 reactionsread 8 August 2026
Photo

Оформляем пресейвик и ждем релиза!!! 🔉ОФОРМИТЬ 🔉

custom 52223892994413195188custom 54045295380906722576custom 52197880396135946092custom 52219682552073562931custom 53778556308139643611

10 Oct 2025, 17:54 UTC≈1,200 views11 reactionsread 8 August 2026

Знаете такого?

custom 52223892994413195187custom 52197880396135946092custom 59990223841688341812

10 Oct 2025, 17:54 UTC≈1,090 views17 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 52197880396135946099custom 53778556308139643614custom 54541128309890257524

29 Sept 2025, 11:44 UTC≈1,180 views22 reactions1 Starread 8 August 2026
Video

XX.10.2025

custom 53778556308139643619custom 52197880396135946097custom 52223892994413195185custom 54045295380906722571

25 Sept 2025, 10:05 UTC≈1,130 views9 reactionsread 8 August 2026
Photo

Solo Way - Вою на луну обложка - jayann mix by - beatsbyspr1tey СЛУШАТЬ ВЕЗДЕ🔊

custom 52219682552073562934custom 59990223841688341813custom 54045295380906722572

25 Sept 2025, 10:05 UTC923 views4 reactionsread 8 August 2026

Всем привет!! Как ваши дела? Тут наш знакомый песенку выложил послушайте, поддержите молодого

custom 52197880396135946093custom 52219682552073562931

21 Sept 2025, 15:32 UTC950 views12 reactionsread 8 August 2026

Ну как вы там? Соскучились?

custom 54541128309890257525custom 59990223841688341815custom 53778556308139643612

21 Sept 2025, 15:32 UTC924 views24 reactions2 Starsread 8 August 2026
Video message

Video message, posted without a caption

custom 52197880396135946099custom 52223892994413195187custom 53778556308139643616custom 59990223841688341812

7 Sept 2025, 11:56 UTC≈1,080 views33 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 521978803961359460911custom 54541128309890257527custom 59990223841688341816custom 53778556308139643615custom 54045295380906722573custom 52223892994413195181

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 986,089 of 1,340,412entries 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

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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Lingering Pain” (@Lingering_Pain), 185 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Lingering_Pain.

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.