Розыгрыш 200⭐️ Хочешь получить 200 Stars? Тогда участвуй! Условия участия: 1 — Подпишись на все каналы ниже. 2 — Нажми кнопку «Участвую». 3 — Дождись итогов — победитель будет выбран когда будет 200 участников. 💬 Выплаты и отзывы: @KHuga_OT3uBoB 📢 Наши каналы: 1. TRAINING CAMP 2. TRAINING CAMP CHAT

Channel
ТДМ ПРАВИЛА | TDM RULES
@WorldTournamentRules
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
284subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002559857514 |
|---|---|
| Type | Channel |
| Username | @WorldTournamentRules |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/WorldTournamentRules |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 17:03 | 284 | +1 |
| 7 Aug 2026, 03:16 | 283 | no change |
| 7 Aug 2026, 03:06 | 283 | first reading |
Engagement
20 posts held, back to 25 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 59.5%
- avg views ÷ 284 subscribers
- Avg views / post
- 169
- 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.
| Window | Rolling 30 days · latest post in window 17 July 2026 |
|---|---|
| Posts held | 20 (25 November 2025 – 17 July 2026) |
| Views total | 169 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 03:16 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.
Recent posts
.
🇷🇺Навигация|Navigation🇪🇺 [🇷🇺] Правила 1x1 — Нажми [🇷🇺] Айос Стор — Нажми [🇷🇺] Андроид Стор — Нажми [🇷🇺] Регламент — Нажми [🇷🇺] Регламент Ивента — Нажми [🇷🇺] ДЛЯ ЧАТА ТУРА — Нажми [🇷🇺] КАК ОТПРАВЛЯТЬ СТОР — Нажми [🇪🇺] Rules 1x1 — Press [🇪🇺] iOS Stor — Press [🇪🇺] Android Stor — Press [🇪🇺] Regulations - Press [🇪🇺] FOR THE TOUR CHAT — Press [🇪🇺] HOW TO SEND A STORE - Press OFFICIAL TOURNAMENT RULES!
[🇪🇺] Regulations: 1 - Day 1/16 23:00 - 23:00 Moscow time Before the first victory 2 - Day 1/8 23:00 - 23:00 Moscow time Before the first victory 3 - Day 1/4 23:00 - 23:00 Moscow time Before the first victory 4 - Day 1/2 23:00 - 23:00 Moscow time Before the first victory 5 - Day 1/1 23:00 - 23:00 Moscow time Up to two victories The final game can be held immediately after the semi-final by agreement of 2 finalis…
[🇪🇺] HOW TO SEND A STORE: Example: AK6AR 🇷🇺 @ak6arJr • After the game, write down the page. • Send to the organizer (Required as in the example in the photo)
4. Behavior. 1. Concerted actions are allowed only for the sake of voice communication (evidenty is required). • In other cases, the opponent has the right to kill. 2. Any insult to the organizer entails disqualification. 3. The winner has the right to stay without action for a total of no more than one minute per game. • If the time is exceeded, the match is replayed (except in some cases).
5. Technical conditions. 1. A player can leave the game only if: • card bug; • ping from eighty and above. • Exit is possible in the first thirty seconds (re-exit at this time = defeat). • Exit after thirty seconds = defeat. 2. You have ten minutes to enter the lobby. • Being late is considered a defeat. 3. The player who entered the lobby first chooses a slot. • In the second game, the slots change.
6. Recording and Checking 1. It is forbidden to delete the match recording until the organizer confirms the victory. 2. A full match recording is required. • The entire match (10 minutes minimum) must be recorded — if there is no recording, it counts as a defeat. • Upon request, the recording must be sent within 30 minutes to the opponent or organizer. • The recording quality must be at least 480p. • No fast-forwar…
7. Prohibitions 1. It is strictly forbidden to use VPNs, Control Configuration apps, WireGuard, cheats, screen stretching, STS, any DNS servers, or account sharing/transfer. • Violation = immediate disqualification. 2. The use of bugs or glitches is prohibited. • If damage is dealt through a bug, the next kill will not be counted. 3. If a player gets stuck in textures and kills the opponent, the kill is deducted. …
8. Other 1. If a player kills the opponent using any weapon other than M416 or a pistol, that player automatically loses. • The second player is free to act as they wish, including leaving the match. 2. Slot transfer is allowed only before the tournament starts. 3. After a match ends, players have 10 minutes to report violations or submit complaints. • After this time, no complaints will be accepted. 4. The final …
9. Decision-Making 1. The score submission (store) is mandatory for any match result — win, loss, or draw. • Complaints against an opponent will not be accepted without a store. • A video that does not include at least three required points of the store is considered an invalid store. 2. Situational Decisions: ⸻ Situation №1 Player #1 (won): • Wrong score/record • Late full record Player #2 (lost): • Wrong score…
[🇪🇺] 🍎 iOS Stor: 📱 AppStore: PUBG login 🔍 Library: «Commands» + «shortcuts» ⚙️ Show all VPN ⚙️ Show the server’s DNS ⚙️ Show iOS version (from 18.0, less = tp) • show the serial number. ⚙️ Show all hidden applications (by any method)
Showing the 12 most recent of 20 posts we hold for @WorldTournamentRules. 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.
Mentions
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@WorldTournamentRules named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 4 posts, 8 August 2026 – 8 August 2026
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“ТДМ ПРАВИЛА | TDM RULES” (@WorldTournamentRules), 284 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/WorldTournamentRules.
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.