نکته آخر ، کمتر 7 ساعت تا افزایش بعدی قیمت هست https://t.me/JaryanPool/19138
❤6,100🔥5,540🥰1,380👍331👏1🤩1

Channel
@JaryanPool
On this record: Topic · Observations · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Domains linked from posts · Cite this entry
2,335,069subscribers
+596,151 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001125067725 |
|---|---|
| Type | Channel |
| Username | @JaryanPool |
| Description | با ما باش سوددهی سالیانه بالای ۱۰ هزار درصد ، ❤️ « بزرگترین جریان پول ایران » ارتباط با ما » @JPool_admin |
| Created | Between 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/JaryanPool |
Crypto & trading — 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 100% 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.
On 71 of the 136 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.1153 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /1923430 Aug 2026, 18:32 UTC | 55 minutes | 16,600 → 24,400at least +7,700 | 4,669 → 4,676at most +17 | +888.0 |
| /1923430 Aug 2026, 18:32 UTC | 36 minutes | 24,400 → 29,000at least +4,500 | 4,676 → 4,679at most +13 | +518.9 |
| /1923430 Aug 2026, 18:32 UTC | 33 minutes | 29,000 → 33,600at least +4,500 | 4,679 → 4,679at most +10 | +518.9 |
| /1923430 Aug 2026, 18:32 UTC | 67 minutes | 33,600 → 41,200at least +7,500 | 4,679 → 4,679at most +10 | +864.9 |
| /1923530 Aug 2026, 18:33 UTC | 55 minutes | 16,300 → 24,400at least +8,000 | 4,264 → 4,278at most +24 | +922.6 |
| /1923530 Aug 2026, 18:33 UTC | 36 minutes | 24,400 → 29,000at least +4,500 | 4,278 → 4,292at most +24 | +518.9 |
| /1923530 Aug 2026, 18:33 UTC | 33 minutes | 29,000 → 33,800at least +4,700 | 4,292 → 4,293at most +11 | +542.0 |
| /1923530 Aug 2026, 18:33 UTC | 67 minutes | 33,800 → 41,700at least +7,800 | 4,293 → 4,294at most +11 | +899.5 |
| /1923730 Aug 2026, 18:35 UTC | 55 minutes | 16,900 → 25,900at least +8,900 | 4,611 → 4,661at most +60 | +1026.4 |
| /1923730 Aug 2026, 18:35 UTC | 36 minutes | 25,900 → 31,000at least +5,000 | 4,661 → 4,672at most +21 | +576.6 |
| /1923730 Aug 2026, 18:35 UTC | 33 minutes | 31,000 → 36,300at least +5,200 | 4,672 → 4,693at most +31 | +599.7 |
| /1923730 Aug 2026, 18:35 UTC | 67 minutes | 36,300 → 45,000at least +8,600 | 4,693 → 4,705at most +22 | +991.8 |
| /1918816 Aug 2026, 17:05 UTC | 42 minutes | 8,120 → 9,640at least +1,510 | 4,343 → 4,346at most +13 | +174.1 |
| /1918816 Aug 2026, 17:05 UTC | 84 minutes | 11,800 → 14,300at least +2,400 | 4,357 → 4,359at most +12 | +276.8 |
| /1918816 Aug 2026, 17:05 UTC | 11 hours | 15,500 → 24,400at least +8,800 | 4,359 → 4,373at most +24 | +1014.8 |
| /1918916 Aug 2026, 17:06 UTC | 42 minutes | 8,580 → 10,400at least +1,720 | 4,508 → 4,510at most +12 | +198.4 |
| /1918916 Aug 2026, 17:06 UTC | 84 minutes | 12,800 → 15,800at least +2,900 | 4,520 → 4,520at most +10 | +334.4 |
| /1918916 Aug 2026, 17:06 UTC | 11 hours | 17,200 → 27,800at least +10,500 | 4,520 → 4,530at most +20 | +1210.9 |
| /1919016 Aug 2026, 17:07 UTC | 42 minutes | 9,360 → 11,200at least +1,740 | 5,153 → 5,163at most +20 | +200.7 |
| /1919016 Aug 2026, 17:07 UTC | 84 minutes | 13,800 → 17,000at least +3,100 | 5,164 → 5,175at most +21 | +357.5 |
| /1919016 Aug 2026, 17:07 UTC | 11 hours | 18,500 → 29,900at least +11,300 | 5,175 → 5,186at most +21 | +1303.1 |
| /1919116 Aug 2026, 17:07 UTC | 42 minutes | 8,740 → 10,600at least +1,760 | 4,470 → 4,473at most +13 | +203.0 |
| /1919116 Aug 2026, 17:07 UTC | 84 minutes | 13,400 → 16,700at least +3,200 | 4,484 → 4,487at most +13 | +369.0 |
| /1919116 Aug 2026, 17:07 UTC | 11 hours | 18,300 → 30,000at least +11,600 | 4,498 → 4,509at most +21 | +1337.7 |
| /1919216 Aug 2026, 17:08 UTC | 42 minutes | 8,450 → 10,500at least +1,950 | 4,262 → 4,281at most +29 | +224.9 |
| /1919216 Aug 2026, 17:08 UTC | 84 minutes | 13,300 → 16,800at least +3,400 | 4,300 → 4,317at most +27 | +392.1 |
| /1919216 Aug 2026, 17:08 UTC | 11 hours | 18,400 → 30,700at least +12,200 | 4,321 → 4,349at most +38 | +1406.9 |
| /1920519 Aug 2026, 16:18 UTC | 40 minutes | 8,740 → 11,200at least +2,360 | 4,752 → 4,774at most +32 | +272.2 |
| /1920519 Aug 2026, 16:18 UTC | 55 minutes | 12,900 → 15,600at least +2,600 | 4,786 → 4,798at most +22 | +299.8 |
| /1920519 Aug 2026, 16:18 UTC | 65 minutes | 15,600 → 18,500at least +2,800 | 4,798 → 4,811at most +23 | +322.9 |
| /1922926 Aug 2026, 18:28 UTC | 35 minutes | 9,040 → 10,600at least +1,460 | 4,268 → 4,272at most +14 | +168.4 |
| /1922926 Aug 2026, 18:28 UTC | 40 minutes | 10,600 → 12,400at least +1,700 | 4,272 → 4,289at most +27 | +196.0 |
| /1922926 Aug 2026, 18:28 UTC | 2 days | 209,000 → 305,000at least +95,000 | 24,296 → 24,306at most +110 | +10955.5 |
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 key view_reaction_decoupling, last confirmed 8 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 22:19 | 2,335,069 | +52,955 |
| 4 Sept 2026, 05:36 | 2,282,114 | +87,146 |
| 2 Sept 2026, 21:35 | 2,194,968 | +73,367 |
| 1 Sept 2026, 18:59 | 2,121,601 | +126,294 |
| 31 Aug 2026, 17:07 | 1,995,307 | +103,477 |
| 30 Aug 2026, 15:34 | 1,891,830 | +21,363 |
| 29 Aug 2026, 13:34 | 1,870,467 | +2,455 |
| 28 Aug 2026, 15:14 | 1,868,012 | +1,206 |
| 27 Aug 2026, 13:44 | 1,866,806 | +559 |
| 26 Aug 2026, 16:23 | 1,866,247 | -1,737 |
| 25 Aug 2026, 19:23 | 1,867,984 | +1,188 |
| 24 Aug 2026, 18:15 | 1,866,796 | +6,888 |
| 23 Aug 2026, 02:57 | 1,859,908 | +25,333 |
| 21 Aug 2026, 16:28 | 1,834,575 | +12,525 |
| 20 Aug 2026, 13:11 | 1,822,050 | +9,670 |
| 19 Aug 2026, 16:34 | 1,812,380 | +4,720 |
| 18 Aug 2026, 19:56 | 1,807,660 | +7,167 |
| 17 Aug 2026, 22:23 | 1,800,493 | +12,356 |
| 16 Aug 2026, 22:05 | 1,788,137 | -3,817 |
| 15 Aug 2026, 11:47 | 1,791,954 | first reading |
164 posts held, back to 1 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 70 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 8 September 2026 |
|---|---|
| Posts held | 164 (1 August 2026 – 8 September 2026) |
| Views total | 14,935,200 |
| Reactions total | 1,270,315 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Sept 2026, 01:12 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 8 September 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.
Measured directly from 7 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 136 of this channel’s own posts over the last 30 days: across 121 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 24 hours of being posted; a typical post has already reached 36.5% of its 24-hour view count within the first hour, and 60.5% within the first six; the median 24-hour reach across those posts is 33,900 views — 1.45% of this channel’s own subscriber count (90th percentile 109,000).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /193028 Sept 2026, 13:15 UTC | 1721 minutes – 12 hours old | 19,200 views ~13,353 reactions | 60 minutes: 15,159 interp. → 3.0 hours: 16,500 → 6.0 hours: 17,800 → 12 hours: 19,200still climbing at last reading | not yet at 24h | 28 minutesprovisional — final view count still climbing |
| /193018 Sept 2026, 13:14 UTC | 1722 minutes – 12 hours old | 19,200 views ~13,351 reactions | 60 minutes: 15,300 → 3.0 hours: 16,600 → 6.0 hours: 17,800 → 12 hours: 19,200still climbing at last reading | not yet at 24h | 22 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /193008 Sept 2026, 13:14 UTC | 1723 minutes – 12 hours old | 19,000 views ~13,439 reactions | 60 minutes: 15,300 → 3.0 hours: 16,500 → 6.0 hours: 17,700 → 12 hours: 19,000still climbing at last reading | not yet at 24h | 23 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /192998 Sept 2026, 13:13 UTC | 1724 minutes – 12 hours old | 18,300 views ~13,193 reactions | 60 minutes: 15,100 → 3.0 hours: 16,200 → 6.0 hours: 17,200 → 12 hours: 18,300still climbing at last reading | not yet at 24h | 24 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /192988 Sept 2026, 13:01 UTC | 1735 minutes – 12 hours old | 18,400 views ~13,414 reactions | 60 minutes: 15,468 interp. → 3.0 hours: 16,513 interp. → 6.0 hours: 17,500 → 12 hours: 18,400still climbing at last reading | not yet at 24h | 35 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /192978 Sept 2026, 12:57 UTC | 1739 minutes – 12 hours old | 18,300 views ~13,277 reactions | 60 minutes: 15,474 interp. → 3.0 hours: 16,587 interp. → 6.0 hours: 17,500 → 12 hours: 18,300views have flattened out | not yet at 24h | 39 minutesupper bound — already past half at first reading |
| /192968 Sept 2026, 12:56 UTC | 1740 minutes – 12 hours old | 19,500 views ~14,129 reactions | 60 minutes: 15,333 interp. → 3.0 hours: 17,582 interp. → 6.0 hours: 18,600 → 12 hours: 19,500still climbing at last reading | not yet at 24h | 40 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /192958 Sept 2026, 12:54 UTC | 1888 seconds – 12 hours old | 19,200 views ~13,232 reactions | 60 minutes: 15,743 interp. → 3.0 hours: 17,067 interp. → 6.0 hours: 18,200 → 12 hours: 19,200still climbing at last reading | not yet at 24h | 27 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.
1,403,767 reactions across 164 posts, in 7 distinct kinds. The most used accounts for 25.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 363,841 | 25.9% | |
| 🔥 | 334,729 | 23.8% | |
| 👍 | 265,275 | 18.9% | |
| 🥰 | 244,116 | 17.4% | |
| 😍 | 75,446 | 5.37% | |
| 👏 | 60,864 | 4.34% | |
| 🤩 | 59,496 | 4.24% |
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 164 of the 164 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 1,403,767 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 164 most recent posts we hold, published 1 August 2026 to 8 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @JaryanPool. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 164 most recent posts we hold for this entry, published 1 August 2026 to 8 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
نکته آخر ، کمتر 7 ساعت تا افزایش بعدی قیمت هست https://t.me/JaryanPool/19138
❤6,100🔥5,540🥰1,380👍331👏1🤩1
نکته مهمترش اینه سایت solscan و BscSacn که میلیونها بازدید روزانه داره و قوانین فوق امنیتی بالا که اعتبار بالایی داره تبلیغ پاندا رو کرده !! میگیری که چیمیگم
🔥5,450❤3,840👍2,280🥰1,780🤩1
صرافی هر ارزی که لیست میکنه امنیت و معتبر بودن پروژه رو چک میکنه ، هزار نوع احراز و مدارک میگیره بعد لیستش میکنه ، بعد لانچش میکنه پاندا در پنج صرافی لیست شده biconomy nexdax indoex vindax Hotcoin داخل کوین مارکت کپ لیست شده و از همه مهمتر تیک ابی و تأیید رسمی در CoinMarketCap برای افزایش اعتبار و اثبات هویت رسمی پروژه
👍6,000🔥3,780🥰3,070❤588👏1
سوال بعضی از دوستان واقعا جالبه پاندا که معرفی کردی معتبر هست ‼️ ما هنوز بهش اعتماد نداریم
🔥6,070👍3,330❤2,710🥰1,080👏2😍1
این پروژه چقدر قویه که فکر میکردم من و چند کانال خارجی در موردش حرف میزدن 😅 اما داستان فراتر از این حرفاس که کل دنیا دارن میبینش این تبلیغات ، اعتبار پروژه رو برای من روی 100 میبره
🔥5,460👍3,960❤3,610🥰383😍1
یک رویکرد جهانی برای پاندا داره اتفاق میفته منتظر خبرهای بینظیر باید باشیم
🥰5,730❤4,170🔥3,050👍322👏3🤩2
پاندایی که من معرفی کردم قبل همه داخل وبسایات های بزرگ که میلیونها بازدید داره راجبش صحبت و تبلیغ میشه میدونی که این وبسایتها کاملا پروژه رو چک میکنن✅
🔥12,100👍784❤646🥰596🤩2👏1
solscan
🔥5,840🥰4,490👍1,780❤1,120👏2
BscSacn
❤5,330🔥4,910🥰1,860👍1,070👏2
ببین با چی برخورد کردم ، واقعا عجیبه
👍7,310🔥4,290❤1,060🥰697😍4
درود رفقا ❤️ یک خبر جالب و عجیب امروز داشتم ارزهای مختلف خودم و تو شبکه های مختلف چک میکردم
👍10,100🔥1,870🥰1,150❤603😍5👏3
من دیگه حرفی ندارم!!! شب بخیر🤯
🥰10,100❤2,280🔥952👍410👏6🤩3😍3
Showing the 12 most recent of 164 posts we hold for @JaryanPool. 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.
@JaryanPool edited 3 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.
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.
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 20 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
5 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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“🐋💸 جـریان پـول” (@JaryanPool), 2,335,069 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/JaryanPool.
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.