Telegram RegisterThe public register of Telegram
Telegram profile photo for Love Story Копейск

Channel

Love Story Копейск

@lovestory_kopeysk

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

6,282subscribers

+41 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002104570985
TypeChannel
Username@lovestory_kopeysk
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live4 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/lovestory_kopeysk

Growth

6,2336,2826,257.57 August 2026 — 6,241 subscribers7 August 2026 — 6,241 subscribers8 August 2026 — 6,242 subscribers15 August 2026 — 6,237 subscribers21 August 2026 — 6,233 subscribers25 August 2026 — 6,235 subscribers28 August 2026 — 6,244 subscribers31 August 2026 — 6,270 subscribers4 September 2026 — 6,282 subscribers7 August 20264 September 2026
9 measurements spanning 27 days, net +41. 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 6,226–6,289 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 06:366,282+12
31 Aug 2026, 17:036,270+26
28 Aug 2026, 11:136,244+9
25 Aug 2026, 01:446,235+2
21 Aug 2026, 07:096,233-4
15 Aug 2026, 15:126,237-5
8 Aug 2026, 15:496,242+1
7 Aug 2026, 19:326,241no change
7 Aug 2026, 19:266,241first reading

Engagement

64 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 7 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
23.5%
avg views ÷ 6,282 subscribers
Avg views / post
1,480
19 posts measured
Reaction rate
0.884%
reactions ÷ views · ER floor
Posts in window
19
of 64 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 17 of 19 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held64 (6 August 202612 August 2026)
Views total28,088
Reactions total220
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 03:23 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
12s
Average length
12s

Measured directly from 1 video 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

1,231 reactions across 60 posts, in 23 distinct kinds. The most used accounts for 17.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏21517.5%
custom 537510061974698315520016.2%
🔥19515.8%
😭16113.1%
👎1149.26%
👍705.69%
🤬514.14%
413.33%
🍓403.25%
🥰262.11%
🗿241.95%
🤯120.975%
💔110.894%
😁110.894%
🙈100.812%
90.731%
🎄80.65%
😍80.65%
😱80.65%
💊60.487%
3 further kinds110.894%

Custom emoji. One 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 count beside it is Telegram’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 60 of the 64 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 1,231 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 64 most recent posts we hold, published 6 August 2026 to 12 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

12 Aug 2026, 02:57 UTC128 views8 reactionsread 12 August 2026
Photo

чтобы потом не говорили, что летом не были на море ❤️подписаться | предложить пост 🫱LoveStory Копейск в MAX

👍5💊2😁1

11 Aug 2026, 17:22 UTC≈1,180 views9 reactionsread 12 August 2026

Кто в какой колледж/универ/школу поступает в этом году?

🍓6custom 537510061974698315521

11 Aug 2026, 13:20 UTC≈1,460 views16 reactionsread 12 August 2026

мальчики, которые сегодня 11.08 втроем несли знак пешеходного перехода примерно в 15:18 вы очень крутые

12🔥2😭1🙏1

11 Aug 2026, 11:57 UTC≈1,550 views8 reactionsread 12 August 2026

Пацан, который 5 августа на велике дал мне пять, и вы с друзьями катались возле нас, найдись пожалуйста, пообщаемся, если не против конечно Это все происходило на славе Админу не дождливых дней 🙏

🥰8

11 Aug 2026, 10:04 UTC≈1,550 viewsread 12 August 2026

Увидел девушку возле детской больницы утром примерно, оч понравилось хочу познакомиться. Была одета в коричневые штаны и розовую футболку. Найдись 🙏

11 Aug 2026, 08:44 UTC≈1,650 views9 reactionsread 12 August 2026

Всем привет, хочу попросить совета. У меня сейчас проколота бровь, и мне кажется, она мигрирует, поэтому я хочу уговорить маму проколоть мне нос (септум). Но мама говорит, что разрешит проколоть крыло и только камушек, а мне это не нравится. Я не знаю, как убедить её на септум. Хочу попросить вас написать, как можно её убедить на септум.

👍6🔥1🙏1custom 53751006197469831551

11 Aug 2026, 06:29 UTC≈1,770 views63 reactionsread 12 August 2026
Photo

Достаём сапы Если мы не едем на море, то море у нас 🌊

🔥485👍4😍3🍓2🤯1

11 Aug 2026, 06:20 UTC≈1,650 viewsread 12 August 2026

11 августа, +- 10 утра, светленький мальчик с длинными волосами в фиксе на кассе самообслужки стоял, тебе по моему сотрудница помогала классные проколы, найдись пжшка

11 Aug 2026, 04:45 UTC≈1,500 views14 reactionsread 12 August 2026
Forwarded from @podslushano_174Photo

‼️ВНИМАНИЕ‼️ ⚡️⚡️На территории Челябинской области сегодня, 11 августа с 09:25, объявлен режим «Беспилотная опасность» Оставайтесь дома и не подходите к окнам или пройдите в укрытие. Если Вы находитесь на улице или в автотранспорте, укройтесь в здании, подземном переходе или паркинге. Возможны перебои мобильного интернета. 🙏Будьте бдительны и осторожны! При обнаружении БВС или его частей сообщайте по телефону «112»

🤬6😭4👍1🔥1😁1😱1

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

Posts edited after publishing

@lovestory_kopeysk edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
10 August 2026
Most recent edit
10 August 2026

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

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.

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

“Love Story Копейск” (@lovestory_kopeysk), 6,282 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/lovestory_kopeysk.

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.