Telegram RegisterThe public register of Telegram
Telegram profile photo for ищу сп|друзейᵗᶦᵃᶰ²

Channel

ищу сп|друзейᵗᶦᵃᶰ²

@isdvrt

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

7,768subscribers

+2,099 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-1002296816203
TypeChannel
Username@isdvrt
Description""𝗦𝗘𝗔𝗥𝗖𝗛 𝗔𝗚𝗘𝗡𝗖𝗬"" ➤ 𝗶𝘀𝗱 𝗰𝗵𝗮𝘁 @chatwnr @chatwns ➤ 𝗼𝘄𝗻𝗲𝗿 @infotizu ➤ 𝗯𝗼𝘁 @tianisd_bot ➤ 𝘃𝗽 @silnev ➤ 𝗽𝗿𝗶𝗰𝗲 @vrtnmu ➤ 𝘀𝘁𝗮𝗿𝘁 03.11.2024
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live9 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/isdvrt

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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
@isdvrt/11497 · this entry10 Aug 2026, 10:21 UTC@isdcutiepie/548018 Aug 2026, 07:57 UTC1.008 days
@isdvrt/11513 · this entry11 Aug 2026, 21:55 UTC@isdcutiepie/664726 Aug 2026, 17:53 UTC1.0015 days
@isdvrt/12824 · this entry1 Nov 2026, 20:05 UTC@isdcutiepie/113604 Nov 2026, 16:58 UTC1.003 days
@isdcutiepie/115156 Nov 2026, 04:30 UTC@isdvrt/12868 · this entry6 Nov 2026, 07:50 UTC1.003.3 hours
@isdvrt/12867 · this entry6 Nov 2026, 05:40 UTC@isdcutiepie/115206 Nov 2026, 06:04 UTC1.0025 minutes
@isdcutiepie/115786 Nov 2026, 17:00 UTC@isdvrt/12885 · this entry7 Nov 2026, 06:36 UTC1.0014 hours
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
@isdcutiepie8 (8/8 hand-verifiable sample passed)1.0042 hoursthis entry (6–2)
@isdvti7 (7/7 hand-verifiable sample passed)1.0026 hoursthis entry (4–3)
@north_isd5 (5/5 hand-verifiable sample passed)1.0029 hours@north_isd (3–2)
@isdasp5 (5/5 hand-verifiable sample passed)1.0025 hours@isdasp (3–2)

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 78 comparable posts for this entry, running 6 August 2026 to 10 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).

Views per post sit far below this size band

44.5 average views per post against 7,588 subscribers — an engagement rate of 0.586%. Across the 16,385 registered channels in the same cohort — 3,183–9,999 subscribers, posting mainly in Russian — the middle half sit between 6.90% and 25.3%, with a median of 13.6%.

What this was computed from
Window30 days (6 October 2026 – 5 November 2026)
Posts measured31 of 31 published in the window (31 exact, 0 rounded by Telegram)
Views totalled1,379
Mature posts only0.65% over 24 posts read at least 24h after publication
Subscribers7,588 measured 3 November 2026
Cohortb3162:rus · 16,385 channels · p10 3.55% · p25 6.90% · p50 13.6% · p75 25.3% · p90 41.1%
Position in cohort0.812th percentile · 1/23 the cohort median
Uncertainty±0.038% of the figure, from Telegram’s rounding
Post languageRussian · 96.3% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the keys clone_mutual · clone_source · err_low, last confirmed 11 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

5,6697,7686,718.57 August 2026 — 5,669 subscribers7 August 2026 — 5,669 subscribers7 August 2026 — 5,670 subscribers10 August 2026 — 5,757 subscribers13 August 2026 — 5,843 subscribers16 August 2026 — 5,885 subscribers19 August 2026 — 5,866 subscribers23 August 2026 — 5,808 subscribers26 August 2026 — 5,795 subscribers29 August 2026 — 5,789 subscribers1 September 2026 — 5,829 subscribers6 September 2026 — 5,894 subscribers11 September 2026 — 5,978 subscribers14 September 2026 — 5,962 subscribers19 September 2026 — 6,019 subscribers29 September 2026 — 6,801 subscribers6 October 2026 — 7,152 subscribers12 October 2026 — 7,365 subscribers15 October 2026 — 7,400 subscribers18 October 2026 — 7,326 subscribers22 October 2026 — 7,411 subscribers25 October 2026 — 7,430 subscribers28 October 2026 — 7,595 subscribers30 October 2026 — 7,611 subscribers3 November 2026 — 7,588 subscribers6 November 2026 — 7,586 subscribers9 November 2026 — 7,768 subscribers7 August 20269 November 2026
27 measurements spanning 94 days, net +2,099. 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 5,354–8,083 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
9 Nov 2026, 16:567,768+182
6 Nov 2026, 07:107,586-2
3 Nov 2026, 02:067,588-23
30 Oct 2026, 17:277,611+16
28 Oct 2026, 04:107,595+165
25 Oct 2026, 01:487,430+19
22 Oct 2026, 01:367,411+85
18 Oct 2026, 20:587,326-74
15 Oct 2026, 13:297,400+35
12 Oct 2026, 23:517,365+213
6 Oct 2026, 13:597,152+351
29 Sept 2026, 19:566,801+782
19 Sept 2026, 08:576,019+57
14 Sept 2026, 16:165,962-16
11 Sept 2026, 08:165,978+84
6 Sept 2026, 03:565,894+65
1 Sept 2026, 18:235,829+40
29 Aug 2026, 15:155,789-6
26 Aug 2026, 06:465,795-13
23 Aug 2026, 02:085,808first reading

Engagement

132 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 24 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.15%
avg views ÷ 7,768 subscribers
Avg views / post
89.6
70 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
72
of 132 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 2 of 70 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 11 November 2026
Posts held132 (6 August 2026 – 11 November 2026)
Views total6,271
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 14: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

Photos
≈12,100
Videos
≈343
Links
≈6,500

Lifetime counters from Telegram’s own channel header, read 11 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
9s
Average length
9s

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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 72 posts held from the last 30 days (0%) 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).

11 Nov 2026, 03:04 UTC68 viewsread 11 November 2026
Photo

⚠Грамотных с острым умом в чат по бтс. Приласкаем, поцелуем, понежим.

Signed Māybě `b1²⁶⁹🏴

10 Nov 2026, 08:12 UTC170 viewsread 11 November 2026
Photo

👋 ☺️ поиске активных нью в нашу прелестную кф! поможем влиться, всегда открыты к новым знакомствам. также есть свободные места админов 👍 инфо: @moceriskye 😎

Signed Arès

10 Nov 2026, 07:22 UTC145 viewsread 11 November 2026
Photo

💼Старшего брата мне/кентов18+ ❤️Узб, Кз, Кыргыз, Даг - жду 🔕Гетеро. ✈️Связь - Messenger - Anon

Signed Arès

9 Nov 2026, 22:49 UTC121 viewsread 11 November 2026
Photo

общения и не против вз связь - @gwvxnjkn меньше 16,кф - бан

Signed ᅠᅠᅠ﹫𝑩𝒓𝒖𝒏𝒚𝒂 ᅠᅠᅠ

9 Nov 2026, 19:54 UTC121 viewsread 11 November 2026
Photo

🌟Серьезного мне в лс 18+ ❤️Узб, Кз, Кыргыз, Даг - газ, давайте ❤️Нытики, нотвирт, молчуны - мимо. ❤️В приоритете инициативые Гетеро. ✈️Связь - Messenger - Anon

Signed ᅠᅠᅠ﹫𝑩𝒓𝒖𝒏𝒚𝒂 ᅠᅠᅠ

9 Nov 2026, 11:50 UTC153 viewsread 11 November 2026
Photo

→ ⠀、ꤦ★﹕ проверка сп !!¡⠀ Ꞌ ₊ ↰ ⤹ хотите проверить на верность свою вторую половинку? или, быть может, узнать, взаимны ли чувства вашего друга к вам? ⤸ в таком случае ꜜ мы ждём вас ꜜ ( @proverkaspvel )

Signed ᅠᅠᅠ﹫𝑩𝒓𝒖𝒏𝒚𝒂 ᅠᅠᅠ

9 Nov 2026, 09:54 UTC138 viewsread 11 November 2026
Photo

знакомств свободному чонгуку нытики,занятые,нотвирт,общение на вечер — бан 16+ рж. чп — -1мск. связь — @sertersaf

Signed Arès●ЗАВАЛ

9 Nov 2026, 09:38 UTC114 viewsread 11 November 2026
Photo

хочу поистине интересных собеседников. общение без обязательств и нытья. возраст, пол, перс - не имеют никакого значения. iMessage.

Signed Arès●ЗАВАЛ

8 Nov 2026, 21:07 UTC142 viewsread 11 November 2026
Photo

хэон, 18, -1 мск. в поиске доминантного, щедрого, строгого и местами ревнивого возлюбленного постарше, кентов тоже можно. написать мне - @HE1NQW_bot с юзом и намерениями. дамы, нотвирт, кф, занятые, общение на вечер - бан.

Signed ᅠᅠᅠ﹫𝑩𝒓𝒖𝒏𝒚𝒂 ᅠᅠᅠ

8 Nov 2026, 17:28 UTC152 viewsread 11 November 2026
Photo

───────────────────────── 🏎 Устал от скучных каналов, где остаётся только листать посты? 🚦 Хочется скорости, азарта и немного безумия? 🏁 Хочу показать вам канал 𝐃𝐑𝐈𝐕𝐄𝐑’𝐒 𝐏𝐀𝐑𝐀𝐃𝐈𝐒𝐄 — канал, где каждый день начинается с зелёного света и превращается в настоящее приключение на трассе. 🏁 Интерактивные игры позволяют не просто наблюдать, а принимать решения и становиться частью происходящего. ⠀ ⠀ ⠀ ⠀ ⠀ ───────────────────…

Signed ᅠᅠᅠ﹫𝑩𝒓𝒖𝒏𝒚𝒂 ᅠᅠᅠ

8 Nov 2026, 13:48 UTC129 viewsread 11 November 2026
Photo

Ищу админов в интерактив канал, который скоро откроется. За хорошую работу буду кидать подарки. @AREV1S

Signed Māybě `b1²⁶⁹🏴

8 Nov 2026, 13:48 UTC121 viewsread 11 November 2026
Photo

это место хранит в себе много секретов..Хотите узнать, что это за место и что за секреты? Что-ж, я расскажу вам о.. Love — новый интерактив, который ищет своих жертв, в свой город! Он вам найдет счастье, вашу судьбу, конечно, если вы узнаете его суть. Мы будем Рады видеть вас на нашем канале и ценим каждого подписчика! Так же, мы ищем стажеров, но об этом вы узнаете на нашем канале! Заходите и узнавайте больше сек…

Signed Māybě `b1²⁶⁹🏴

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

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.

“ищу сп|друзейᵗᶦᵃᶰ²” (@isdvrt), 7,768 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/isdvrt.

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.