Telegram RegisterThe public register of Telegram

Channel

Bitunix 🏦 صرافی بیت یونیکس

@Bitunixe

2 usernames

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

222,429subscribers

-1,828 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001321649951
TypeChannel
Usernames@Bitunixe @bitunixfund
Descriptionچنل آموزشی صرافی بیت یونیکس🐬 ارتباط با ما: @Alielon سیگنال دهی: @ChartsPrice لینک ثبت نام در صرافی Bitunix 👇🐳 https://www.bitunix.com/register?vipCode=signal
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held13
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/Bitunixe

Topic

Marketing & affiliate — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 41% 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. They sit inside a group of 3 channels that share the same post bodies with each other. 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
@Bitunixe/13890 · this entry9 Feb 2026, 05:32 UTC@arzwhale/20349 Feb 2026, 14:35 UTC1.009.1 hours
@Bitunixe/13895 · this entry25 Feb 2026, 15:49 UTC@arzwhale/203525 Feb 2026, 16:59 UTC1.0071 minutes
@Bitunixe/13899 · this entry18 Apr 2026, 05:31 UTC@arzwhale/203818 Apr 2026, 06:28 UTC1.0057 minutes
@Bitunixe/13903 · this entry14 May 2026, 17:51 UTC@arzwhale/204114 May 2026, 18:11 UTC1.0021 minutes
@arzwhale/204014 May 2026, 18:11 UTC@Bitunixe/13909 · this entry1 Jun 2026, 16:30 UTC1.0018 days
@Bitunixe/13912 · this entry1 Jul 2026, 15:05 UTC@arzwhale/20471 Jul 2026, 17:00 UTC1.001.9 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@arzwhale7 (7/7 hand-verifiable sample passed)1.0071 minutesthis entry (61)

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 1 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 20 comparable posts for this entry, running 10 May 2025 to 5 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 3, the earliest publisher we hold is @ToobitFarsi. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 8 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 2 other registered channels, 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

222,429224,257223,3436 August 2026 — 224,257 subscribers7 August 2026 — 224,257 subscribers7 August 2026 — 224,134 subscribers8 August 2026 — 223,800 subscribers8 August 2026 — 223,800 subscribers9 August 2026 — 223,480 subscribers9 August 2026 — 223,480 subscribers10 August 2026 — 223,207 subscribers10 August 2026 — 223,124 subscribers11 August 2026 — 222,846 subscribers11 August 2026 — 222,810 subscribers12 August 2026 — 222,559 subscribers12 August 2026 — 222,429 subscribers6 August 202612 August 2026
13 measurements spanning 6 days, net -1,828. 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 222,155–224,531 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 13:44222,429-130
12 Aug 2026, 02:02222,559-251
11 Aug 2026, 12:58222,810-36
11 Aug 2026, 03:28222,846-278
10 Aug 2026, 09:42223,124-83
10 Aug 2026, 00:02223,207-273
9 Aug 2026, 06:11223,480no change
9 Aug 2026, 01:31223,480-320
8 Aug 2026, 05:14223,800no change
8 Aug 2026, 04:22223,800-334
7 Aug 2026, 07:41224,134-123
7 Aug 2026, 02:56224,257no change
6 Aug 2026, 20:33224,257first reading

Engagement

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

ERR · 30 days
5.84%
avg views ÷ 222,429 subscribers
Avg views / post
13,000
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 20 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 5 August 2026
Posts held20 (10 May 20255 August 2026)
Views total13,000
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 17:58 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
59
Videos
11
Links
71

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

5 Aug 2026, 13:37 UTC≈13,000 viewsread 12 August 2026
Photo

🔥 کمپین تابستانی بیت‌یونیکس شروع شد🥳! در این رویداد سفر معاملاتی خود را در بیت یونیکس آغاز کنید و تا 1,000 دلار پاداش قابل ضرر دریافت کنید. ✅ توجه داشته باشید که این رویداد فقط مختص به کاربران ثبت‌نامی از طرف کد تخفیف Signal می‌باشد. شرایط رویداد📑: 📥 رویداد واریز و معامله: 🔫. مبلغ حداقلی 100 تتر واریز کنید و حجم معاملات خود را در فیوچرز به 5 هزار دلار برسانید و 50 دلار پاداش دریافت کنید. 🔫. مبلغ حداقلی 500 تتر وار

1 Jul 2026, 15:05 UTC≈31,600 viewsread 12 August 2026
Photo

🔥 کمپین بزرگ بیت‌یونیکس شروع شد🥳! واریز کنید و سفر معاملاتی خود را در بیت یونیکس آغاز کنید و تا 2,500 دلار پاداش برای هر کاربر و 60 درصد کش‌بک دریافت کنید. ✅ توجه داشته باشید که این رویداد فقط مختص به کاربران ثبت‌نامی از طرف کد تخفیف Signal می‌باشد. شرایط رویداد📑: 📥 واریز: 🔫. مبلغ حداقلی 100 تتر واریز کنید و پس از انجام یک معامله‌ فیوچرز، 50 دلار پاداش دریافت کنید. 🔫. مبلغ حداقلی 500 تتر واریز کنید و پس از انجام ی

1 Jun 2026, 16:30 UTC≈32,500 viewsread 12 August 2026
Photo

🔥 کمپین ویژه واریز بیت‌یونیکس، وقت برگشت به مارکته🥳! در این رویداد هرکاربر می‌تواند با واریز و معامله، تا 1,500 دلار پاداش قابل ضرر و کش‌بک 50 درصدی دریافت کند. ✅ توجه داشته باشید که این رویداد فقط مختص به کاربران ثبت‌نامی از طرف کد تخفیف Signal می‌باشد. شرایط رویداد📑: 1️⃣. مبلغ حداقلی 100 تتر واریز کنید و با انجام اولین معامله‌ 40 دلار پاداش اضافی دریافت کنید. 2️⃣. مبلغ حداقلی 500 تتر واریز کنید و با انجام اولین

14 May 2026, 17:51 UTC≈34,600 viewsread 12 August 2026

📢 خبر خوب برای کاربران عزیز بیت‌یونیکس🥳! نسخه نت ملی بیت‌یونیکس در بازار منتشر شد، می‌توانید با استفاده از این نسخه بدون فیلتر به صرافی متصل شوید و معامله کنید. ➡️ https://cafebazaar.ir/app/io.bitunix.android 🔥 @Bitunixe

18 Apr 2026, 05:31 UTC≈35,700 viewsread 12 August 2026
Photo

🔥 کمپین جدید بیت‌یونیکس شروع شد🥳! واریز کنید و سفر معاملاتی خود را در بیت یونیکس آغاز کنید و تا 2,300 دلار پاداش دریافت کنید. ✅ توجه داشته باشید که این رویداد فقط مختص به کاربران ثبت‌نامی از طرف کد تخفیف Signal می‌باشد. شرایط رویداد📑: 📥 واریز و معامله: 🔫. مبلغ حداقلی 100 تتر واریز کنید و پس از انجام یک معامله‌ فیوچرز، 30 دلار پاداش دریافت کنید. 🔫. مبلغ حداقلی 500 تتر واریز کنید و پس از انجام یک معامله‌ فیوچرز، 150

25 Feb 2026, 15:49 UTC≈38,900 viewsread 12 August 2026
Photo

📢 آپدیت جدید صرافی بیت‌یونیکس! بخش جدید TradFi به مارکت فیوچرز Bitunix اضافه شد. 🗣این بخش امکان مشاهده سریع بازارهای مالی سنتی مثل طلا "XAUUSDT"، نقره "XAGUSDT"، پلاتین و پالادیوم را در یک دسته‌بندی مجزا فراهم می‌کند. ⬇️ مسیر دسترسی: Markets → Marketplace → Futures → TradFi 🔥 @Bitunixe

9 Feb 2026, 05:32 UTC≈121,000 viewsread 12 August 2026
Photo

🔥 کمپین ویژه واریز بیت‌یونیکس🥳! در این رویداد هرکاربر می‌تواند با واریز و معامله، تا 500 دلار پاداش قابل ضرر و کش‌بک 50 درصدی دریافت کند. ✅ توجه داشته باشید که این رویداد فقط مختص به کاربران ثبت‌نامی از طرف کد تخفیف Signal می‌باشد. شرایط رویداد📑: 🔫. مبلغ حداقلی 50 تتر واریز کنید و با انجام اولین معامله‌ 20 دلار پاداش اضافی دریافت کنید. 🔫. مبلغ حداقلی 100 تتر واریز کنید و با انجام اولین معامله‌ 40 دلار پاداش اضافی

31 Jan 2026, 05:31 UTC≈70,800 viewsread 12 August 2026
Photo

🔥 کمپين حمايتی اختلال شبکه بیت‌یونیکس؛ جبران خسارت 100 درصدی با USDT نقدی👍! به منظور حمايت از کاربرانی که به دليل اختلالات اخير شبکه امکان مديريت پوزيشن های خود را نداشته‌اند و در راستای مسئولیت اجتماعی‌مان بیت‌یونیکس کمپين حمايتی اختلال شبکه را راه اندازی کرده‌ و برای پوزيشن های ليکوييد شده‌ی واجد شرايط، 100% جبران خسارت با USDT نقدی را ارائه می‌دهد. 🗓 بازه کمپين (بازه محاسبه) بازه پوزيشن های ليکوييد شده: 19 دی تا

3 Dec 2025, 05:33 UTC≈389,000 viewsread 12 August 2026
Photo

🔥 کمپین جدید بیت‌یونیکس شروع شد | تا 1,200 دلار پاداش بدون محدودیت در تعداد معامله و لوریج برای هر کاربر🥳! در این رویداد هرکاربر می‌تواند با واریز و معامله، جوایز ویژه بدون محدودیت دریافت کند. ✅ توجه داشته باشید که این رویداد فقط مختص به کاربران ثبت‌نامی از طرف کد تخفیف Signal می‌باشد. شرایط رویداد📑: 1️⃣. رویداد واریز: 🔫. مبلغ حداقلی 100 تتر واریز کنید و با انجام اولین معامله‌ی خود 20 دلار پاداش اضافی دریافت کنید.

11 Nov 2025, 05:34 UTC≈90,900 viewsread 12 August 2026
Photo

🔥 کمپین جدید بیت‌یونیکس شروع شد | تا 1,200 دلار پاداش بدون محدودیت در تعداد معامله و لوریج برای هر کاربر🥳! در این رویداد هرکاربر می‌تواند با واریز و معامله، جوایز ویژه بدون محدودیت دریافت کند. ✅ توجه داشته باشید که این رویداد فقط مختص به کاربران ثبت‌نامی از طرف کد تخفیف Signal می‌باشد. شرایط رویداد📑: 1️⃣. رویداد واریز: 🔫. مبلغ حداقلی 100 تتر واریز کنید و با انجام اولین معامله‌ی خود 20 دلار پاداش اضافی دریافت کنید.

16 Oct 2025, 15:10 UTC≈48,600 viewsread 12 August 2026
Photo

🔥 کمپین ویژه بیت‌یونیکس شروع شد | فرصت طلایی برای تریدرها🥳! در این رویداد هرکاربر می‌تواند با واریز و معامله، جوایز ویژه بدون محدودیت دریافت کند. ✅ توجه داشته باشید که این رویداد فقط مختص به کاربران ثبت‌نامی از طرف کد تخفیف Signal می‌باشد. شرایط رویداد📑: 1️⃣. رویداد واریز: 🔫. مبلغ حداقلی 50 تتر واریز کنید و با انجام اولین معامله‌ی خود 10 دلار پاداش اضافی دریافت کنید. 🔫. مبلغ حداقلی 100 تتر واریز کنید و با انجام او

29 Aug 2025, 13:10 UTC≈64,600 viewsread 12 August 2026
Photo

🔥 رویداد داغ بیت‌یونیکس شروع شد🥳! در این رویداد هرکاربر می‌تواند تا 40 درصد کش‌بک و 1,300 دلار پاداش بدون محدودیت دریافت کند. ✅ توجه داشته باشید که این رویداد فقط مختص به کاربران ثبت‌نامی از طرف کد تخفیف Signal می‌باشد. شرایط رویداد📑: کافیه با لینک مستقیم مجموعه‌ما و یا کد تخفیف Signal در صرافی Bitunix ثبت‌نام کنید و اولین واریز و اولین معامله فیوچرز خود را انجام دهید و تا 20 دلار پاداش دریافت کنيد. 1️⃣رویداد واری

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

Citation-graph rank

Citation-graph rank — 267,629 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 3 registered channels — 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.

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.

Domains linked from posts

2 domainsthis channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

www.bitunix.comregistrable domain: bitunix.com15 posts · 29 August 2025 – 5 August 2026 · example post
cafebazaar.ir1 post · 14 May 2026 – 14 May 2026 · example post

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.

“Bitunix 🏦 صرافی بیت یونیکس” (@Bitunixe), 222,429 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Bitunixe.

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.