@LinkedinDownloadBot
❤🔥2

Channel
@un_logs
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
16,347subscribers
-298 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002353265775 |
|---|---|
| Type | Channel |
| Username | @un_logs |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/un_logs |
Marketing & affiliate — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 14:39 | 16,347 | -17 |
| 16 Sept 2026, 05:19 | 16,364 | -9 |
| 14 Sept 2026, 10:40 | 16,373 | -13 |
| 12 Sept 2026, 18:39 | 16,386 | -15 |
| 10 Sept 2026, 19:39 | 16,401 | -26 |
| 7 Sept 2026, 20:01 | 16,427 | -15 |
| 4 Sept 2026, 21:59 | 16,442 | -10 |
| 3 Sept 2026, 09:03 | 16,452 | -3 |
| 2 Sept 2026, 05:16 | 16,455 | -6 |
| 1 Sept 2026, 08:17 | 16,461 | -10 |
| 31 Aug 2026, 09:57 | 16,471 | -5 |
| 30 Aug 2026, 11:48 | 16,476 | -8 |
| 29 Aug 2026, 09:34 | 16,484 | -4 |
| 28 Aug 2026, 10:47 | 16,488 | -1 |
| 27 Aug 2026, 07:53 | 16,489 | -8 |
| 26 Aug 2026, 11:05 | 16,497 | -6 |
| 25 Aug 2026, 09:55 | 16,503 | -10 |
| 24 Aug 2026, 11:04 | 16,513 | -13 |
| 22 Aug 2026, 17:34 | 16,526 | -9 |
| 21 Aug 2026, 08:59 | 16,535 | first reading |
21 posts held, back to 27 June 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 52 pages of 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 21 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.
404 reactions across 21 posts, in 3 distinct kinds. The most used accounts for 58.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 236 | 58.4% | |
| 🔥 | 98 | 24.3% | |
| ❤🔥 | 70 | 17.3% |
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 21 of the 21 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 404 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 27 June 2025 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.
@LinkedinDownloadBot
❤🔥2
Using link shorteners to monetize your content? Your links can be bypassed and most creators don’t even realize it. That means lost clicks and lost revenue. Use your own link wrapper with captcha protection to prevent bypassing and protect your earnings. ✅ 7-day free trial ❄️ t.me/asprin_devs 👇🏼👇🏼👇🏼👇🏼👇🏼👇🏼👇🏼 🔗 https://links.asprin.dev
❤11🔥3
Train with shubham - latest batch Batch - 9 https://t.me/+olurlWueyoM2MzA1
❤21🔥5
Sigma 8 full course nothing Missing https://t.me/+9LGxAJCid79iNzY1
❤🔥19❤8🔥7
Jsmastery Nextjs 15 - Full Course https://t.me/nextjs15_mastery
❤🔥16❤13🔥8
Code With Harry full Course https://t.me/codewithharry_datascience
🔥15❤🔥8❤7
Tips for crafting your resume: Apply the XYZ method to clearly show impact. Avoid buzzwords and repetitive phrases. Include metrics to quantify your achievements. Highlight what you’ve accomplished, not just responsibility. After drafting 1) Check your ATS score. 2) If it’s below 90, refine and update your resume. 3) Use ChatGPT to iteratively improve your LaTeX code and achieve a 92+ ATS score. Resume Site https://w…
❤13🔥3
Market is Tuff now in 2025 more tuff in 2026 FOCUS MORE ON DSA + CORE CSE + OOPS IF TIER 1 FOCUS MORE ON DEVELOPMENT + SYSTEM DESIGN IF Going HIGH PACKAGE JOBS HEAVY IF TEIR 2-3 OPEN SOURCE CONTRIBUTION GOOD ONLINE PRESENCE 3 BADASS PROJECT ATS FRIENDLY RESUME - 90 score 7.5 + CPGA Also I am Busy Nowadays in job and cllg Please Don't beg Courses on telegram. There are so many Resources Use of it. No run after new…
❤76🔥9❤🔥7
Arpit Redis https://t.me/+mvuiLanHeJ8yMWE0
🔥5❤1
https://t.me/TopCodingInterviewProblems
❤7❤🔥2
All The Links, Will Be expired Before 30 July Means new users can't enter in that group, To protect the resources
🔥28❤15❤🔥7
Keerti purswani - Advanced C++ With Networking https://t.me/+bLIigFlps3VkNDFl
❤2
Showing the 12 most recent of 21 posts we hold for @un_logs. 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.
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.
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.
@un_logs named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“UNLOCKED LOGS” (@un_logs), 16,347 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/un_logs.
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.