Telegram RegisterThe public register of Telegram

Channel

Liberty Connection

@Liberty_conection

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

3,414subscribers

-4 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001560220962
TypeChannel
Username@Liberty_conection
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/Liberty_conection

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 90% 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.

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 word for word on 1 other registered channel. 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
@Turbo_Channel_Fast/64710 Jun 2026, 21:05 UTC@Liberty_conection/1009 · this entry10 Jun 2026, 21:05 UTC1.00under a minute
@Turbo_Channel_Fast/65011 Jun 2026, 14:58 UTC@Liberty_conection/1013 · this entry11 Jun 2026, 15:08 UTC1.0010 minutes
@Liberty_conection/1006 · this entry10 Jun 2026, 05:44 UTC@Turbo_Channel_Fast/65213 Jun 2026, 08:12 UTC1.003 days
@Turbo_Channel_Fast/6648 Jul 2026, 21:06 UTC@Liberty_conection/1019 · this entry12 Jul 2026, 16:45 UTC1.004 days
@Turbo_Channel_Fast/66719 Jul 2026, 07:14 UTC@Liberty_conection/1021 · this entry19 Jul 2026, 07:14 UTC1.00under a minute
@Turbo_Channel_Fast/66820 Jul 2026, 07:50 UTC@Liberty_conection/1022 · this entry20 Jul 2026, 07:50 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@Turbo_Channel_Fast9 (8/8 hand-verifiable sample passed)0.99under a minute@Turbo_Channel_Fast (72)

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. None of the 6 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 14 comparable posts for this entry, running 30 May 2026 to 6 August 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).

Across the whole group of 2, the earliest publisher we hold is @Liberty_conection — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

3,4143,4183,4166 August 2026 — 3,418 subscribers6 August 2026 — 3,418 subscribers9 August 2026 — 3,416 subscribers12 August 2026 — 3,414 subscribers6 August 202612 August 2026
4 measurements spanning 6 days, net -4. 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 3,413–3,419 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 03:343,414-2
9 Aug 2026, 11:113,416-2
6 Aug 2026, 06:013,418no change
6 Aug 2026, 04:493,418first reading

Engagement

21 posts held, back to 30 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
23.2%
avg views ÷ 3,414 subscribers
Avg views / post
792
11 posts measured
Reaction rate
0.207%
reactions ÷ views · ER floor
Posts in window
12
of 21 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 10 of 11 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 6 August 2026
Posts held21 (30 May 20266 August 2026)
Views total8,717
Reactions total16
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:15 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
36s
Average length
12s

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

28 reactions across 15 posts, in 2 distinct kinds. The most used accounts for 92.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2692.9%
👍27.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 18 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 35reactions 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 30 May 2026 to 6 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

6 Aug 2026, 17:06 UTC260 views2 reactionsread 7 August 2026

👆اکانت های مولتی حتما این کار رو انجام بدید 📌

1👍1

6 Aug 2026, 07:58 UTC352 views1 reactionsread 7 August 2026
Video

📣 کاربران عزیزی که اشتراک مولتی کانفیگ تهیه کردند جهت افزایش کیفیت ,لطفاً یک بار لینک اشتراک خود را بروز رسانی کنید . ⚙️ میتونید از ویدیو های پست کمک بگیرید.

1

5 Aug 2026, 10:24 UTC426 views1 reactionsread 7 August 2026

✅ تمامی سرور ها به سرور پک آپ انتقال پیدا کرد

1

5 Aug 2026, 10:05 UTC425 views1 reactionsread 7 August 2026

❌ دیتا سنتر ایران از دسترس خارج شده در حال پیگیری مشکل هستیم

1

2 Aug 2026, 19:59 UTC688 views1 reactionsread 7 August 2026

❌ تعدادی از سرور ها دچار اختلال شدن در حال رفع مشکلیم

1

30 Jul 2026, 20:06 UTC970 viewsread 7 August 2026

دریافت آخرین نسخه برنامه v2ray 📥 https://github.com/2dust/v2rayNG/releases/download/2.2.6/v2rayNG_2.2.6-fdroid_arm64-v8a.apk 🔗

23 Jul 2026, 17:16 UTC≈1,380 views2 reactionsread 7 August 2026
Photo

🚨مزایای سرویس های 🛰 مولتی کانفیگ – چند کشوری 🌍 ⚡️دسترسی به چند کشور به طور همزمان 🇫🇮🇩🇪🇹🇷🇱🇺🇳🇱🇺🇸 🗺 آیپی تمامی کشور ها ثابت بوده و تغییر نمیکند ✔️تمامی اکانت های ما تانل هستند با تمام اپراتورها کاملا سازگار هستند. 🏐اتصال پایدار به علت وجود چند دیتا سنتر ایرانی و خارجی همزمان حتی در مواقع اختلال🛑 و نت ملی🛜 🎆مشاهده لحظه ای باقیمانده حجم و زمان کانفیگ هم از داخل برنامه هم از لینک خود vpn مناسب کاربر های حرفه اینترنت م

2

20 Jul 2026, 07:50 UTC≈1,300 views1 reactionsread 7 August 2026

⚠️ اطلاعیه دوستان، دامنه 2 تا از سرور های کانفیگ‌های تک فیلتر شده. 1- لطفاً وارد لینک ساب (Subscription) خود شوید و کانفیگ با اطلاعات جدید رو از لینک ساب دریافت کنید . 2 - آموزش تعویض کانفیگ اگر کانفیگ شما دچار مشکل شده، مراحل زیر را انجام دهید: 1️⃣ وارد حساب کاربری خود شوید. 2️⃣ بخش سرویس‌های فعال را باز کنید. 3️⃣ روی کانفیگ موردنظر خود بزنید. 4️⃣ گزینه «تعویض کانفیگ» را انتخاب کنید. 5️⃣ پس از ساخته شدن کانفی

1

19 Jul 2026, 07:14 UTC≈1,180 views3 reactionsread 7 August 2026

✅ اطلاعیه با توجه به اینکه تمامی سرویس‌ها پیش از آغاز عملیات به سرور پشتیبان (Backup) منتقل شدند، نیازی به انتشار اکانت موقت در کانال نبود. پس از پایان عملیات ارتقای شبکه و هنگام بازگرداندن سرویس‌ها به سرور اصلی، ممکن است برای چند لحظه قطعی یا اختلال کوتاهی در اتصال احساس شود. از صبوری و همراهی شما سپاسگزاریم. 🙏

3

18 Jul 2026, 20:40 UTC≈1,040 views3 reactionsread 7 August 2026

کاربران گرامی، 📢 به اطلاع می‌رساند به‌منظور ارتقای شبکه دیتاسنتر، سرویس‌های تک کانفیگ و تعدادی از لوکیشن‌های مولتی کانفیگ ممکن است در بازه زمانی ۱۰:۰۰ الی ۱۱:۳۰ روز یکشنبه با اختلال یا قطعی موقت مواجه شوند. ⚠️ جهت جلوگیری از اختلال در اتصال، از ساعت ۹:۰۰ اکانت موقت در کانال قرار خواهد گرفت. 🔒 از صبوری و همراهی شما سپاسگزاریم. 🙏

3

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

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

“Liberty Connection” (@Liberty_conection), 3,414 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Liberty_conection.

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.