Telegram RegisterThe public register of Telegram
Telegram profile photo for 🔞△OSINT 69 and Sons Presents△🔞

Channel

🔞△OSINT 69 and Sons Presents△🔞

@osint_69

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

8,680subscribers

+49 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-1001901714144
TypeChannel
Username@osint_69
Created29 July 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live2 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/osint_69

Growth

8,6318,6918,6617 August 2026 — 8,631 subscribers7 August 2026 — 8,631 subscribers8 August 2026 — 8,637 subscribers11 August 2026 — 8,660 subscribers14 August 2026 — 8,655 subscribers17 August 2026 — 8,652 subscribers21 August 2026 — 8,667 subscribers24 August 2026 — 8,691 subscribers27 August 2026 — 8,688 subscribers30 August 2026 — 8,686 subscribers2 September 2026 — 8,680 subscribers8,6807 August 20262 September 2026
11 measurements spanning 26 days, net +49. 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,622–8,700 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 22:558,680-6
30 Aug 2026, 23:258,686-2
27 Aug 2026, 19:338,688-3
24 Aug 2026, 23:578,691+24
21 Aug 2026, 04:178,667+15
17 Aug 2026, 17:468,652-3
14 Aug 2026, 15:388,655-5
11 Aug 2026, 05:518,660+23
8 Aug 2026, 14:308,637+6
7 Aug 2026, 20:008,631no change
7 Aug 2026, 19:568,631first reading

Engagement

58 posts held, back to 4 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 26 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
8.07%
avg views ÷ 8,680 subscribers
Avg views / post
700
40 posts measured
Reaction rate
1.35%
reactions ÷ views · ER floor
Posts in window
40
of 58 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 28 August 2026
Posts held58 (4 August 202628 August 2026)
Views total28,017
Reactions total377
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 16:37 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
53m 58s
Average length
59s

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

539 reactions across 58 posts, in 19 distinct kinds. The most used accounts for 23.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥12623.4%
11321.0%
👏8916.5%
custom 53259452387353095146411.9%
😁387.05%
🤣275.01%
👍152.78%
🎉132.41%
🏆112.04%
👻112.04%
🥰91.67%
🫡91.67%
🕊40.742%
👌30.557%
🌭20.371%
😍20.371%
10.186%
💩10.186%
😱10.186%

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

Measured over the 58 most recent posts we hold, published 4 August 2026 to 28 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

28 Aug 2026, 08:52 UTC110 views3 reactionsread 28 August 2026
Forwarded from @robert_magyarVideo

ЙОБЛИК☠️ДНЯ 9 472☠️🩸хробаки протягом 01-27 серпня Онлайн-табло СБС «ПІДРАХУЙКА» https://sbs-group.army/ МАДЯР🇺🇦 28.08.26 🔵МАДЯР🎞МАДЯР👥МАДЯР 👥RB📷МАДЯР 🇺🇦СБС онлайн«ПІДРАХУЙКА»СБС

🔥21

27 Aug 2026, 08:34 UTC274 views5 reactionsread 28 August 2026
Forwarded from @umftteamVideo

Що буде, якщо намагатися збити FPV-дрон дошкою? Відповідь — наприкінці відео 🤫 Пілоти SIGNUM розмотали ворожу піхоту на Лиманському напрямку. Оштрафували мотоцикліста, покарали окупантів у лісах та відправили в останню путь тих, хто намагався відбиватися. А наприкінці — пошматований окупант. Саме так виглядає черговий день для російської піхоти. 🗡Instagram | X | YouTube | Facebook | Телеграм 💵Підтримай вогонь SI

😁3🔥2

27 Aug 2026, 08:25 UTC234 views5 reactionsread 28 August 2026
Forwarded from @robert_magyarVideo

ЙОБЛИК☠️ДНЯ 9 004☠️🩸хробаки протягом 01-26 серпня Онлайн-табло СБС «ПІДРАХУЙКА» https://sbs-group.army/ МАДЯР🇺🇦 27.08.26 🔵МАДЯР🎞МАДЯР👥МАДЯР 👥RB📷МАДЯР 🇺🇦СБС онлайн«ПІДРАХУЙКА»СБС

🔥4👏1

26 Aug 2026, 12:21 UTC330 views7 reactionsread 28 August 2026
Forwarded from @robert_magyarVideo

ЙОБЛИК☠️ДНЯ 8 601☠️🩸хробак протягом 01-25 серпня Онлайн-табло СБС «ПІДРАХУЙКА» https://sbs-group.army/ МАДЯР🇺🇦 26.08.26 🔵МАДЯР🎞МАДЯР👥МАДЯР 👥RB📷МАДЯР 🇺🇦СБС онлайн«ПІДРАХУЙКА»СБС

6🕊1

25 Aug 2026, 17:38 UTC404 views11 reactionsread 28 August 2026
Forwarded from @deadrussianslol2Video

Rat eats the body of a russian https://t.me/spartan_ngu/3372

custom 532594523873530951492

25 Aug 2026, 17:32 UTC393 views7 reactionsread 28 August 2026
Forwarded from @trozsusumy117Video

Підрозділи 117 ОБр ТрО продовжують нищити особовий склад та техніку ворога✊ Дивіться чергову 🔥 нарізку бойової роботи наших воїнів. Дякуємо за службу та захист🫡 Хочеш перемагати разом з нами? Приєднуйся до підрозділів БпС! ☎️073-8000-117

👏5🥰2

25 Aug 2026, 11:07 UTC399 views19 reactionsread 28 August 2026
Forwarded from @dead_zigger_storageVideo

18+ | #TZD of the day: A Russian invader meets his inevitable fate and burns alive somewhere in Donetsk, eastern Ukraine Dead Zigger Storage | Group Chat

🔥181

25 Aug 2026, 00:45 UTC450 views9 reactionsread 28 August 2026
Forwarded from @rubaka_77Video

⚠️ 18+ Відео містить чутливі кадри. Незалежність — наше право. Захищати її — наш обов’язок. Знищувати тих, хто прийшов її відібрати, — наша робота. Ті, хто звик жити без свободи, вирішили забрати її у вільного народу. На українській землі цей вибір привів їх до закономірного фіналу.💀

🔥5custom 53259452387353095142👏1👻1

24 Aug 2026, 15:51 UTC507 views16 reactionsread 28 August 2026
Forwarded from @LegionEuropaVideo

🇺🇦🇺🇦 🇷🇺⚡️— A Ukrainian sabotage and reconnaissance group collects the bodies of neutralized Russian invaders after a successful ambush in a forested area in the Dobropillya direction. 🇪🇺 Legion Europa | Group Chat

👏11🫡31🔥1

24 Aug 2026, 08:38 UTC598 views9 reactionsread 28 August 2026
Video

С Днём Независимости Украины! В честь этого решили умыть кацапу хрюкальник золотым дождём и напомнить новые реалии для них. P.S. в целях безопасности еблет был скрыт. #ЭКСКЛЮЗИВ #ОБОССАННЫЕ ✙ ЛСК ПОДПИСАТЬСЯ ✙

😁5🔥21💩1

24 Aug 2026, 05:25 UTC560 views8 reactionsread 28 August 2026
Forwarded from @robert_magyarVideo

ЙОБЛИК☠️ДНЯ 7 843☠️🩸хробаків протягом 01-23 серпня Онлайн-табло СБС «ПІДРАХУЙКА» https://sbs-group.army/ МАДЯР🇺🇦 24.08.26 🔵МАДЯР🎞МАДЯР👥МАДЯР 👥RB📷МАДЯР 🇺🇦СБС онлайн«ПІДРАХУЙКА»СБС

5🔥3

22 Aug 2026, 10:55 UTC699 views11 reactionsread 28 August 2026
Forwarded from @robert_magyarVideo

ЙОБЛИК☠️ДНЯ 7 145☠️🩸хробаків протягом 01-21 серпня Онлайн-табло СБС «ПІДРАХУЙКА» https://sbs-group.army/ МАДЯР🇺🇦 22.08.26 🔵МАДЯР🎞МАДЯР👥МАДЯР 👥RB📷МАДЯР 🇺🇦СБС онлайн«ПІДРАХУЙКА»СБС

👏6🔥32

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

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

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Warriors Ukrainian🇺🇦
@warriorsukrainian · 41,252
Telegram ranks this channel #20 of 71 here — alongside 70 others — read 29 August 2026
NOELREPORTS 🇪🇺 🇺🇦
@noel_reports · 34,783
Telegram ranks this channel #22 of 74 here — alongside 73 others — read 3 September 2026
UNITED24Media
@United24media · 69,366
Telegram ranks this channel #24 of 85 here — alongside 84 others — read 20 August 2026
Live: Ukraine
@liveukraine_media · 42,758
Telegram ranks this channel #48 of 79 here — alongside 78 others — read 29 August 2026
RFU News — Strategic Geopolitics
@RFU_EN · 50,818
Telegram ranks this channel #50 of 81 here — alongside 80 others — read 25 August 2026
The Kyiv Independent
@KyivIndependent_official · 44,400
Telegram ranks this channel #64 of 89 here — alongside 88 others — read 28 August 2026
Our Wars, Today
@ourwarstoday · 47,431
Telegram ranks this channel #64 of 81 here — alongside 80 others — read 26 August 2026

This channel appears in 7 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“🔞△OSINT 69 and Sons Presents△🔞” (@osint_69), 8,680 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/osint_69.

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.