Telegram RegisterThe public register of Telegram
Telegram profile photo for Ищу тебя | Могилёв

Channel

Ищу тебя | Могилёв

@lfymogilev

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

9,588subscribers

+757 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-1002207546524
TypeChannel
Username@lfymogilev
DescriptionПредложить/удалить пост: t.me/lfymogilev?direct Реклама: @lfybelarus Инстаграм: https://www.instagram.com/lfy.mogilev Админ: @lfyadmin
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live9 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/lfymogilev

Topic

Other / unclassifiable — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 80% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 4 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@itgomel/95459 Aug 2026, 12:15 UTC@lfymogilev/12432 · this entry9 Aug 2026, 12:24 UTC1.0010 minutes
@itgomel/971014 Aug 2026, 16:01 UTC@lfymogilev/12627 · this entry14 Aug 2026, 16:01 UTC1.00under a minute
@lfymogilev/12724 · this entry18 Aug 2026, 13:04 UTC@itgomel/981718 Aug 2026, 13:04 UTC1.00under a minute
@itgomel/996324 Aug 2026, 07:09 UTC@lfymogilev/12894 · this entry24 Aug 2026, 07:10 UTC1.00under a minute
@lfyminsk/197089 Aug 2026, 12:16 UTC@lfymogilev/12432 · this entry9 Aug 2026, 12:24 UTC1.008 minutes
@lfymogilev/12627 · this entry14 Aug 2026, 16:01 UTC@lfyminsk/1983014 Aug 2026, 16:02 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@itgomel10 (8/8 hand-verifiable sample passed)1.00under a minuteeven
@lfyminsk9 (8/8 hand-verifiable sample passed)1.0072 secondsthis entry (5–4)
@lfygrodno9 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (6–3)
@itborisov5 (5/5 hand-verifiable sample passed)1.002 minutesthis entry (4–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 11 of the 11 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 290 comparable posts for this entry, running 6 August 2026 to 12 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the keys clone_mutual · clone_source, last confirmed 13 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

8,8319,5889,209.57 August 2026 — 8,831 subscribers7 August 2026 — 8,854 subscribers11 August 2026 — 8,895 subscribers14 August 2026 — 8,951 subscribers17 August 2026 — 8,981 subscribers20 August 2026 — 9,024 subscribers23 August 2026 — 9,044 subscribers26 August 2026 — 9,049 subscribers29 August 2026 — 9,092 subscribers1 September 2026 — 9,146 subscribers5 September 2026 — 9,185 subscribers10 September 2026 — 9,209 subscribers14 September 2026 — 9,226 subscribers18 September 2026 — 9,229 subscribers27 September 2026 — 9,322 subscribers5 October 2026 — 9,400 subscribers12 October 2026 — 9,456 subscribers15 October 2026 — 9,471 subscribers18 October 2026 — 9,477 subscribers21 October 2026 — 9,511 subscribers24 October 2026 — 9,513 subscribers27 October 2026 — 9,517 subscribers30 October 2026 — 9,524 subscribers2 November 2026 — 9,557 subscribers5 November 2026 — 9,567 subscribers9 November 2026 — 9,588 subscribers7 August 20269 November 2026
26 measurements spanning 94 days, net +757. 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 8,717–9,702 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
9 Nov 2026, 08:459,588+21
5 Nov 2026, 23:209,567+10
2 Nov 2026, 16:009,557+33
30 Oct 2026, 17:369,524+7
27 Oct 2026, 23:569,517+4
24 Oct 2026, 14:279,513+2
21 Oct 2026, 06:189,511+34
18 Oct 2026, 08:569,477+6
15 Oct 2026, 15:519,471+15
12 Oct 2026, 06:389,456+56
5 Oct 2026, 08:169,400+78
27 Sept 2026, 10:009,322+93
18 Sept 2026, 13:019,229+3
14 Sept 2026, 11:579,226+17
10 Sept 2026, 22:409,209+24
5 Sept 2026, 18:389,185+39
1 Sept 2026, 09:439,146+54
29 Aug 2026, 15:349,092+43
26 Aug 2026, 10:339,049+5
23 Aug 2026, 20:579,044first reading

Engagement

581 posts held, back to 6 August 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 54 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
33.8%
avg views ÷ 9,588 subscribers
Avg views / post
3,240
206 posts measured
Reaction rate
0.366%
reactions ÷ views · ER floor
Posts in window
208
of 581 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 November 2026
Posts held581 (6 August 2026 – 13 November 2026)
Views total666,980
Reactions total2,444
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Nov 2026, 01:54 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

Photos
≈5,860
Videos
≈109
Links
≈200

Lifetime counters from Telegram’s own channel header, read 14 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
30s
Average length
15s

Measured directly from 2 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

4,906 reactions across 575 posts, in 58 distinct kinds. The most used accounts for 45.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2,20645.0%
🤣1,16423.7%
❤‍🔥3226.56%
💘2925.95%
🔥1072.18%
😭1042.12%
😍931.90%
😢891.81%
💋771.57%
🙏541.10%
🖕521.06%
🥰410.836%
🐳260.53%
🤨240.489%
😁220.448%
🍓210.428%
🤓170.347%
👍150.306%
🥴140.285%
🙈120.245%
38 further kinds1543.14%

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

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

Telegram’s own ‘edited’ marker: 5 of 208 posts held from the last 30 days (2.40%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

13 Nov 2026, 18:54 UTC≈2,160 views74 reactionsread 14 November 2026

извините что не по теме, кто завтра 14.11 на дубровку???

🤣59❤7💘3😐3💋2

13 Nov 2026, 17:24 UTC≈2,600 views26 reactionsread 14 November 2026
Photo

Ищу девушку, хотел бы познакомиться если не против и тд. Ехала на 4 автобусе, в 14:50 вышла на октябрьском.

🤣14❤5❤‍🔥2🦄2👍1💘1🥰1

13 Nov 2026, 17:24 UTC≈2,590 views3 reactionsread 14 November 2026

ищу парня, сегодня 13 ноября сел в автобус 4 ,вроде как на областной,волосы светлые, был без куртки в черной кофте,ехал так до мовчанского ,потом я вышла ,а он поехал дальше (время 17.05) анон

❤3

13 Nov 2026, 17:23 UTC≈2,580 views5 reactionsread 14 November 2026

Ищу парня, каждое утро выходит на казимировке рост +- 185 темные волосы постоянно в краснай куртке скорое всего учится в торговике Анон

❤3🔥2

13 Nov 2026, 17:23 UTC≈2,560 views3 reactionsread 14 November 2026

извините что не по теме, кто идет сегодня на каток в 21.45? иду один хотелось бы найти с кем можно покататься

🔥3

13 Nov 2026, 15:17 UTC≈3,130 views22 reactionsread 14 November 2026
Photo

Ищу красивую девушку, была в 17:40 на остановке площадь единства с подругой, в 17:46 села на 3 троллейбус, найдись пожалуйста. Админу счастья.

❤8🔥7💘4❤‍🔥2🤣1

13 Nov 2026, 14:04 UTC≈3,270 views19 reactionsread 14 November 2026

здраствуйте извините что не по тебе , кто идет завтра на дубровку , желательно до 16лет , желательно девочки , мальчики тоже возможны

🤣12❤3❤‍🔥2💘1🤬1

13 Nov 2026, 14:03 UTC≈3,270 views6 reactionsread 14 November 2026

ищу мальчика, в 16:30 ехал на 4 автобус в сторону казимировки. Слегка кудрявые волосы, каштанового цвета, приблизительно 180 ростом(может меньше) черная куртка, черные джинсы, и вроде, белые кроссовки. Вышел на орджоникидзе

❤‍🔥3❤2💔1

13 Nov 2026, 12:31 UTC≈3,400 views21 reactionsread 14 November 2026

здравствуйте, извините что не по теме,кто собирается поступать в политехнический? Или кто там уже учится,желательно на маркетолога🙏 Можете рассказать плюсы и минусы. Анон

😭8🤣6❤3😁2💋1😨1

13 Nov 2026, 10:36 UTC≈3,490 views3 reactionsread 14 November 2026

Всем привет, я спрашивала про маркетолога в колледжах и отработки, теперь спрошу такой же вопрос про логиста в торговом колледже Где проходит практика и отработка?🙏

❤3

13 Nov 2026, 10:36 UTC≈3,510 views16 reactionsread 14 November 2026
Photo

Ищу мальчика, ехал в 24 автобусе время примерно 10:25. Переглянулись пару раз, понравился хотелось бы познакомиться. Админу удачи😊

🤣11❤5

Showing the 12 most recent of 581 posts we hold for @lfymogilev. 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 recorded as deleted after publishing

We recorded 2 posts on @lfymogilev as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
11 November 2026
Most recent seen missing
12 November 2026
Median time before seen missing
17 hours
Seen missing in the last 30 days
2

Forward network

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

“Ищу тебя | Могилёв” (@lfymogilev), 9,588 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/lfymogilev.

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.