دلار فردایی تهران ⛳️۲۳۵,۵۰۰ خرید 🔵 دلار فردایی تهران⛳۲۳۶,۰۰۰ فروش⭕️ دلار فردایی تهران ⛳۲۳۵,۵۰۰ معامله✅ #سکه 🏅_حواله 238,700,000 فروش♦️ 💰 #آبشده_نقدی 103,720,000 خرید🔹 ✨ #طلا_گرمی 23,944,409
🔥63🤝17❤14✍5👏5👍2👎1

Channel
@ba_z1
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · View velocity · Reactions · Posts · Posts edited after publishing · Polls · Citations · Handles named that no longer answer · Telegram's recommendations · Domains linked from posts · Cite this entry
1,887,785subscribers
+603,547 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001285237424 |
|---|---|
| Type | Channel |
| Username | @ba_z1 |
| Description | تابع جمهوری اسلامی ایران تبلیغات شخصی👇 @Doolarrr12 هیچ گونه خرید فروش انجام نمیشود و هیچ دخالتی در بازار ارز دلار و خودرو نداریم هر اعتراضی دارید به ایدی ادمین پی ام بدید برسی میشود و در رأس قوانین جمهوری اسلامی ایران هستیم |
| Created | 20 February 2020 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 36 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/ba_z1 |
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 8 August 2026 and assigned it the closest of 31 fixed categories, at 48% 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.
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.
Posts published here appear word for word on 12 other registered channels. They sit inside a group of 464 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @ga_os/9896522 Dec 2025, 06:42 UTC | @ba_z1/95200 · this entry22 Dec 2025, 06:42 UTC | 1.00 | under a minute |
| @ga_os/995858 Jan 2026, 14:53 UTC | @ba_z1/95805 · this entry8 Jan 2026, 14:53 UTC | 1.00 | under a minute |
| @ga_os/1007879 Mar 2026, 14:33 UTC | @ba_z1/97004 · this entry9 Mar 2026, 14:33 UTC | 1.00 | under a minute |
| @ga_os/1010602 Apr 2026, 05:54 UTC | @ba_z1/97277 · this entry2 Apr 2026, 05:54 UTC | 1.00 | under a minute |
| @ga_os/10180010 May 2026, 11:39 UTC | @ba_z1/98002 · this entry10 May 2026, 11:39 UTC | 1.00 | under a minute |
| @ga_os/10191214 May 2026, 16:36 UTC | @ba_z1/98113 · this entry14 May 2026, 16:36 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @ga_os | 4,444 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (2,958–1,486) |
| @se_pz | 4,389 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @se_pz (2,629–1,760) |
| @km_ap | 364 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @km_ap (193–171) |
| @ss_2e | 354 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (204–150) |
| @es_qb | 326 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (185–141) |
| @ir_b0 | 214 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @ir_b0 (122–92) |
| @dolaramz | 15 (8/8 hand-verifiable sample passed) | 1.00 | 7 minutes | this entry (15–0) |
| @ne_wg | 13 (8/8 hand-verifiable sample passed) | 1.00 | 4.8 hours | @ne_wg (8–5) |
| @taladelfan | 12 (8/8 hand-verifiable sample passed) | 1.00 | 10 minutes | this entry (12–0) |
| @fo_rk | 11 (8/8 hand-verifiable sample passed) | 1.00 | 8.9 hours | @fo_rk (8–3) |
| @khabarfouri | 11 (8/8 hand-verifiable sample passed) | 0.99 | 88 minutes | this entry (6–5) |
| @do_l4 | 9 (8/8 hand-verifiable sample passed) | 1.00 | 3.5 hours | this entry (5–4) |
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. 31 of the 4,750 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 4,884 comparable posts for this entry, running 1 November 2025 to 7 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.
Across the whole group of 464, the earliest publisher we hold is @akharinkhabar. That is a statement about our reading window, not a claim of authorship.
On 169 of the 438 posts we watched over 30 days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0195 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /1006218 Sept 2026, 20:35 UTC | 34 minutes | 3,240 → 4,150at least +900 | 360 → 362at most +3 | +17.5 |
| /1006218 Sept 2026, 20:35 UTC | 32 minutes | 4,150 → 4,850at least +690 | 362 → 362at most +1 | +13.4 |
| /1006218 Sept 2026, 20:35 UTC | 34 minutes | 4,850 → 5,740at least +880 | 362 → 364at most +3 | +17.1 |
| /1006218 Sept 2026, 20:35 UTC | 39 minutes | 5,800 → 8,170at least +2,360 | 365 → 365at most +1 | +45.9 |
| /1006218 Sept 2026, 20:35 UTC | 35 minutes | 9,300 → 10,900at least +1,500 | 365 → 365at most +1 | +29.2 |
| /1006218 Sept 2026, 20:35 UTC | 30 minutes | 10,900 → 12,900at least +1,900 | 365 → 365at most +1 | +37.0 |
| /1006459 Sept 2026, 20:49 UTC | 30 minutes | 3,180 → 3,990at least +800 | 353 → 353at most +1 | +15.6 |
| /1006459 Sept 2026, 20:49 UTC | 37 minutes | 4,190 → 4,910at least +710 | 353 → 353at most +1 | +13.8 |
| /1006459 Sept 2026, 20:49 UTC | 20 minutes | 4,960 → 5,950at least +980 | 353 → 353at most +1 | +19.1 |
| /1006459 Sept 2026, 20:49 UTC | 35 minutes | 5,950 → 7,070at least +1,110 | 353 → 353at most +1 | +21.6 |
| /1006459 Sept 2026, 20:49 UTC | 31 minutes | 7,070 → 9,180at least +2,100 | 353 → 353at most +1 | +40.8 |
| /1006459 Sept 2026, 20:49 UTC | 35 minutes | 9,180 → 12,300at least +3,020 | 353 → 353at most +1 | +58.7 |
| /10041930 Aug 2026, 17:32 UTC | 34 minutes | 3,950 → 4,770at least +810 | 353 → 355at most +3 | +15.8 |
| /10041930 Aug 2026, 17:32 UTC | 34 minutes | 4,770 → 6,150at least +1,370 | 355 → 360at most +6 | +26.6 |
| /10041930 Aug 2026, 17:32 UTC | 34 minutes | 6,530 → 7,520at least +980 | 360 → 361at most +2 | +19.1 |
| /10041930 Aug 2026, 17:32 UTC | 30 minutes | 8,520 → 9,850at least +1,320 | 361 → 361at most +1 | +25.7 |
| /10041930 Aug 2026, 17:32 UTC | 36 minutes | 10,900 → 12,800at least +1,800 | 362 → 362at most +1 | +35.0 |
| /1006057 Sept 2026, 20:30 UTC | 34 minutes | 3,480 → 4,340at least +850 | 357 → 358at most +2 | +16.5 |
| /1006057 Sept 2026, 20:30 UTC | 33 minutes | 4,560 → 5,340at least +770 | 358 → 358at most +1 | +15.0 |
| /1006057 Sept 2026, 20:30 UTC | 45 minutes | 5,410 → 6,650at least +1,230 | 358 → 360at most +3 | +23.9 |
| /1006057 Sept 2026, 20:30 UTC | 30 minutes | 6,720 → 9,480at least +2,750 | 360 → 361at most +2 | +53.5 |
| /1006057 Sept 2026, 20:30 UTC | 36 minutes | 9,480 → 14,100at least +4,520 | 361 → 361at most +1 | +87.9 |
| /10044831 Aug 2026, 19:26 UTC | 31 minutes | 4,960 → 6,080at least +1,110 | 355 → 355at most +1 | +21.6 |
| /10044831 Aug 2026, 19:26 UTC | 72 minutes | 6,420 → 7,700at least +1,270 | 358 → 363at most +6 | +24.7 |
| /10044831 Aug 2026, 19:26 UTC | 31 minutes | 7,700 → 9,240at least +1,530 | 363 → 363at most +1 | +29.8 |
| /10044831 Aug 2026, 19:26 UTC | 66 minutes | 10,200 → 12,600at least +2,300 | 363 → 363at most +1 | +44.7 |
| /1004711 Sept 2026, 19:44 UTC | 35 minutes | 5,490 → 6,330at least +830 | 372 → 372at most +1 | +16.1 |
| /1004711 Sept 2026, 19:44 UTC | 34 minutes | 6,580 → 7,880at least +1,290 | 372 → 372at most +1 | +25.1 |
| /1004711 Sept 2026, 19:44 UTC | 31 minutes | 7,960 → 9,950at least +1,980 | 372 → 372at most +1 | +38.5 |
| /1004711 Sept 2026, 19:44 UTC | 35 minutes | 10,000 → 12,100at least +2,000 | 372 → 372at most +1 | +38.9 |
| /1004852 Sept 2026, 13:30 UTC | 32 minutes | 4,620 → 6,610at least +1,980 | 381 → 385at most +5 | +38.5 |
| /1004852 Sept 2026, 13:30 UTC | 32 minutes | 6,610 → 8,140at least +1,520 | 385 → 386at most +2 | +29.6 |
| /1004852 Sept 2026, 13:30 UTC | 31 minutes | 8,140 → 9,490at least +1,340 | 386 → 388at most +3 | +26.1 |
| /1004852 Sept 2026, 13:30 UTC | 35 minutes | 9,490 → 11,300at least +1,710 | 388 → 390at most +3 | +33.3 |
| /1005826 Sept 2026, 19:30 UTC | 30 minutes | 3,160 → 4,520at least +1,350 | 352 → 352at most +1 | +26.3 |
| /1005826 Sept 2026, 19:30 UTC | 24 minutes | 5,940 → 6,970at least +1,020 | 353 → 353at most +1 | +19.8 |
| /1005826 Sept 2026, 19:30 UTC | 34 minutes | 7,040 → 8,570at least +1,520 | 353 → 353at most +1 | +29.6 |
| /1005826 Sept 2026, 19:30 UTC | 36 minutes | 8,630 → 11,900at least +3,170 | 353 → 353at most +1 | +61.7 |
| /10071713 Sept 2026, 20:04 UTC | 33 minutes | 4,620 → 5,750at least +1,120 | 358 → 358at most +1 | +21.8 |
| /10071713 Sept 2026, 20:04 UTC | 57 minutes | 5,750 → 6,750at least +990 | 358 → 359at most +2 | +19.3 |
| /10071713 Sept 2026, 20:04 UTC | 32 minutes | 8,210 → 9,690at least +1,470 | 359 → 359at most +1 | +28.6 |
| /10071713 Sept 2026, 20:04 UTC | 34 minutes | 9,690 → 11,700at least +1,910 | 359 → 359at most +1 | +37.2 |
| /10039929 Aug 2026, 14:32 UTC | 12 minutes | 5,060 → 6,120at least +1,050 | 355 → 356at most +2 | +20.4 |
| /10039929 Aug 2026, 14:32 UTC | 55 minutes | 6,860 → 7,970at least +1,100 | 356 → 357at most +2 | +21.4 |
| /10039929 Aug 2026, 14:32 UTC | 33 minutes | 10,600 → 14,400at least +3,700 | 357 → 357at most +1 | +72.0 |
Expected is the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say. It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the keys clone_copy · clone_mutual · clone_source · view_reaction_decoupling, last confirmed 27 September 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.
This channel’s posts match, word for word or near enough, posts on 463 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.
413 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 20:16 | 1,887,785 | +588,146 |
| 19 Sept 2026, 14:38 | 1,299,639 | -77,265 |
| 17 Sept 2026, 02:38 | 1,376,904 | -25,540 |
| 15 Sept 2026, 06:17 | 1,402,444 | -40,777 |
| 13 Sept 2026, 15:57 | 1,443,221 | -421 |
| 11 Sept 2026, 22:42 | 1,443,642 | +99,347 |
| 9 Sept 2026, 11:40 | 1,344,295 | -6,233 |
| 6 Sept 2026, 04:36 | 1,350,528 | +133,794 |
| 4 Sept 2026, 01:59 | 1,216,734 | +34,089 |
| 2 Sept 2026, 14:24 | 1,182,645 | +49,291 |
| 1 Sept 2026, 16:12 | 1,133,354 | +12,061 |
| 31 Aug 2026, 18:47 | 1,121,293 | -5,632 |
| 30 Aug 2026, 20:12 | 1,126,925 | -17,115 |
| 29 Aug 2026, 17:47 | 1,144,040 | -8,209 |
| 28 Aug 2026, 15:53 | 1,152,249 | +14,248 |
| 27 Aug 2026, 17:36 | 1,138,001 | +72,368 |
| 26 Aug 2026, 15:12 | 1,065,633 | -31,388 |
| 25 Aug 2026, 11:43 | 1,097,021 | -7,218 |
| 24 Aug 2026, 12:38 | 1,104,239 | -32,379 |
| 22 Aug 2026, 21:37 | 1,136,618 | first reading |
6,291 posts held, back to 1 November 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 399 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 27 September 2026 |
|---|---|
| Posts held | 6,291 (1 November 2025 – 27 September 2026) |
| Views total | 9,401,950 |
| Reactions total | 174,356 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 21:05 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.
Lifetime counters from Telegram’s own channel header, read 27 September 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.
Measured directly from 33 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.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 443 of this channel’s own posts over the last 30 days (14 of the 24-hour readings behind this are interpolated, not measured directly): across 387 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 59 minutes of being posted; a typical post has already reached 56.1% of its 24-hour view count within the first hour, and 89.3% within the first six; the median 24-hour reach across those posts is 17,100 views — 0.906% of this channel’s own subscriber count (90th percentile 20,400).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /10092527 Sept 2026, 17:18 UTC | 92 minutes – 3.8 hours old | 14,700 views ~107 reactions | 60 minutes: 9,663 interp. → 3.0 hours: 14,251 interp.still climbing at last reading | not yet at 24h | 45 minutesprovisional — final view count still climbing |
| /10092427 Sept 2026, 16:17 UTC | 1033 minutes – 4.8 hours old | 15,700 views ~106 reactions | 60 minutes: 10,998 interp. → 3.0 hours: 14,669 interp.still climbing at last reading | not yet at 24h | 34 minutesprovisional — final view count still climbing |
| /10092327 Sept 2026, 15:18 UTC | 1123 minutes – 5.8 hours old | 15,800 views ~105 reactions | 60 minutes: 9,392 interp. → 3.0 hours: 14,500 → 6.0 hours: 15,800still climbing at last reading | not yet at 24h | 45 minutesprovisional — final view count still climbing |
| /10092227 Sept 2026, 14:41 UTC | 1230 minutes – 6.4 hours old | 15,300 views ~103 reactions | 60 minutes: 11,700 → 3.0 hours: 13,837 interp. → 6.0 hours: 15,100still climbing at last reading | not yet at 24h | 38 minutesprovisional — final view count still climbing |
| /10092127 Sept 2026, 12:57 UTC | 168 minutes – 8.1 hours old | 18,000 views ~108 reactions | 60 minutes: 13,142 interp. → 3.0 hours: 16,042 interp. → 6.0 hours: 17,500still climbing at last reading | not yet at 24h | 33 minutesprovisional — final view count still climbing |
| /10092027 Sept 2026, 12:04 UTC | 1730 minutes – 9.0 hours old | 16,400 views ~105 reactions | 60 minutes: 12,700 → 3.0 hours: 14,500 → 6.0 hours: 15,800still climbing at last reading | not yet at 24h | 44 minutesprovisional — final view count still climbing |
| /10091927 Sept 2026, 12:04 UTC | 1731 minutes – 9.0 hours old | 18,100 views ~103 reactions | 60 minutes: 14,700 → 3.0 hours: 16,400 → 6.0 hours: 17,500still climbing at last reading | not yet at 24h | 38 minutesprovisional — final view count still climbing |
| /10091827 Sept 2026, 11:09 UTC | 1920 minutes – 9.9 hours old | 16,800 views ~114 reactions | 60 minutes: 13,215 interp. → 3.0 hours: 15,000 → 6.0 hours: 16,200still climbing at last reading | not yet at 24h | 25 minutesprovisional — final view count still climbing |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
207,904 reactions across 966 posts, in 55 distinct kinds. The most used accounts for 20.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👎 | 42,317 | 20.4% | |
| ❤ | 42,048 | 20.2% | |
| 👍 | 41,748 | 20.1% | |
| 🔥 | 41,691 | 20.1% | |
| 👏 | 37,826 | 18.2% | |
| ✍ | 538 | 0.259% | |
| 🤝 | 477 | 0.229% | |
| 🎃 | 279 | 0.134% | |
| 🤬 | 135 | 0.065% | |
| 🖕 | 125 | 0.06% | |
| 🤣 | 78 | 0.038% | |
| 💔 | 66 | 0.032% | |
| 😁 | 63 | 0.03% | |
| 💋 | 57 | 0.027% | |
| 😭 | 52 | 0.025% | |
| 🙉 | 47 | 0.023% | |
| 🥰 | 37 | 0.018% | |
| 👻 | 30 | 0.014% | |
| 🍌 | 27 | 0.013% | |
| 😡 | 23 | 0.011% | |
| 35 further kinds | 240 | 0.115% |
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 995 of the 1,000 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 208,113 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 3 August 2026 to 27 September 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.
دلار فردایی تهران ⛳️۲۳۵,۵۰۰ خرید 🔵 دلار فردایی تهران⛳۲۳۶,۰۰۰ فروش⭕️ دلار فردایی تهران ⛳۲۳۵,۵۰۰ معامله✅ #سکه 🏅_حواله 238,700,000 فروش♦️ 💰 #آبشده_نقدی 103,720,000 خرید🔹 ✨ #طلا_گرمی 23,944,409
🔥63🤝17❤14✍5👏5👍2👎1
دلار فردایی تهران ⛳️235,770 خرید 🔵 دلار فردایی تهران⛳236.270 فروش⭕️ دلار فردایی تهران ⛳235,770 معامله✅ 💰 #آبشده_اتحادیه 103,300,000 فروش♦️ ✨ #طلا_گرمی 23,846,900 💰#تتر[USDT] 235,089فروش♦️
🔥46👏18👍14🤝13✍11❤2👎2
دلار فردایی تهران ⛳️235,660 خرید 🔵 دلار فردایی تهران⛳236.160 فروش⭕️ دلار فردایی تهران ⛳235,660 معامله✅ #سکه 🏅_نقدی 237,500,000 خرید🔹 💰 #آبشده__امروزی 103,405,000 فروش♦️ ✨ #طلا_گرمی 23,871,139 💰#تتر[USDT] 235,511فروش♦️
🤝36✍28🔥16👏9❤8👍4👎3🥰1
دلار فردایی تهران ⛳️236,170 خرید 🔵 دلار فردایی تهران⛳236,670 فروش⭕️ دلار فردایی تهران ⛳236,170 معامله✅ #سکه 🏅_حواله 239,200,000 فروش♦️ 💰 #آبشده_نقدی 103,800,000 خرید🔹 ✨ #طلا_گرمی 23,962,878 💰#تتر[USDT] 235,422خرید🔹
🔥34👏22❤18✍15🤝8👍4👎2
دلار فردایی تهران ⛳️236,140 خرید 🔵 دلار فردایی تهران⛳236,640 فروش⭕️ دلار فردایی تهران ⛳236,140 معامله✅ #سکه 🏅_نقدی 237,800,000 خرید🔹 💰 #آبشده_نقدی 103,900,000 خرید🔹 ✨ #طلا_گرمی 23,985,963 💰#تتر[USDT] 235,442فروش♦️
👍57🤝16✍14🔥9👏7❤2👎2🙉1
دلار فردایی تهران ⛳️236,160 خرید 🔵 دلار فردایی تهران⛳236,660 فروش⭕️ دلار فردایی تهران ⛳236,160 معامله✅ #سکه 🏅_حواله 239,800,000 فروش♦️ 💰 #آبشده_نقدی 103,860,000 فروش♦️ ✨ #طلا_گرمی 23,976,176 💰#تتر[USDT] 235,217خرید🔹
👏42❤29🤝22🔥4✍3👍3👎2
دلار فردایی تهران ⛳️236,160 خرید 🔵 دلار فردایی تهران⛳236,660 فروش⭕️ دلار فردایی تهران ⛳236,160 معامله✅ #سکه 🏅_حواله 239,800,000 فروش♦️ 💰 #آبشده_نقدی 103,860,000 فروش♦️ ✨ #طلا_گرمی 23,976,176 💰#تتر[USDT] 235,217خرید🔹
🔥68✍9❤8👏7🤝6👍3👎2
دلار فردایی تهران ⛳️۲۳۶,۴۰۰ خرید 🔵 دلار فردایی تهران⛳۲۳۶,۹۰۰ فروش⭕️ دلار فردایی تهران ⛳۲۳۶,۴۰۰ معامله✅ 💰#تتر[USDT] 235,558خرید🔹 #سکه 🏅_حواله 239,500,000 فروش♦️ 💰 #آبشده_نقدی 104,050,000 خرید🔹 ✨ #طلا_گرمی 24,020,038
👍33👏33❤18✍17🔥7🤝4👎2
دلار فردایی تهران ⛳️235,870 خرید 🔵 دلار فردایی تهران⛳236.370 فروش⭕️ دلار فردایی تهران ⛳235,870 معامله✅ 💰 #آبشده_نقدی 103,750,000 فروش♦️ ✨ #طلا_گرمی 23,951,335 💰#تتر[USDT] 234,700فروش♦️ #سکه 🏅_حواله 239,500,000 خرید🔹
👍37🔥29✍17❤11🤝9👎2
دلار فردایی تهران ⛳️235,830 خرید 🔵 دلار فردایی تهران⛳236.330 فروش⭕️ دلار فردایی تهران ⛳235,830 معامله✅ #سکه 🏅_حواله 239,000,000 خرید🔹 💰 #آبشده_نقدی 103,650,000 فروش♦️ ✨ #طلا_گرمی 23,928,249 💰#تتر[USDT] 234,701خرید🔹
✍29🔥22🤝19👏18👍14❤4👎2
دلار فردایی تهران ⛳️234,660 خرید 🔵 دلار فردایی تهران⛳235.160 فروش⭕️ دلار فردایی تهران ⛳234,660 معامله✅ 💰#تتر[USDT] 234,430خرید🔹 سکه 🏅⏳ فردایی: 244,100,000 معامله✅ 💰 #آبشده_نقدی 103,640,000 فروش♦️ ✨ #طلا_گرمی 23,925,389
👏46❤22🔥14🤝10👍9✍5👎3
دلار فردایی تهران ⛳️234,660 خرید 🔵 دلار فردایی تهران⛳235.160 فروش⭕️ دلار فردایی تهران ⛳234,660 معامله✅ 💰#تتر[USDT] 233,970فروش♦️ سکه 🏅⏳ فردایی: 244,100,000 معامله✅ 💰 #آبشده_نقدی 103,300,000 خرید🔹 ✨ #طلا_گرمی 23,846,900
❤52✍28👏10🤝10🔥8👎2👍1😡1
Showing the 12 most recent of 6,291 posts we hold for @ba_z1. 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.
@ba_z1 edited 7 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
موافق هستین برای دقایقی لینک vip رو بذارم کانال؟
Shares as published. No per-option vote count is published by Telegram, so none is shown.
《دوستان بخاطر شرایط جنگی و اقتصادی کشور، متاسفانه ضرر اعضا اونقدر زیاد شده که تصمیم گرفتیم لینک Vip رو به مدت ۱ روز آزاد کنیم. موافقید؟》
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 1,000 most recent posts we hold (the sample is capped at 1,000), published 3 August 2026 to 27 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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.
@ba_z1 named 32 handles 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 11 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
78 domains this 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.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“قیمت بازار دلار طلا خودرو” (@ba_z1), 1,887,785 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/ba_z1.
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.