Like basmagy unutman โค๏ธ
Signed Auto Post BOT

Channel
@FULL_SERWERS
On this record: Topic ยท Observations ยท Channels linked by matching posts ยท Growth ยท Engagement ยท What this channel posts ยท Reactions ยท Posts ยท Posts edited after publishing ยท Posts recorded as deleted ยท Citations ยท Cite this entry
17,149subscribers
+0 since we began measuring on 14 November 2026
Risers and fallers across the register ยท movement among entries of 10,000โ31,623.
| Telegram ID | -1002032183406 |
|---|---|
| Type | Channel |
| Username | @FULL_SERWERS |
| Description | ๐ะะฐ ะฝะฐัะตะผ ะบะฐะฝะฐะปะต ๐ะผั ะฟัะฑะปะธะบัะตะผ VPN-ะบะพะดั ะธ ะขะตะปะตะณัะฐะผะผ ะฟัะพะบัะธ ัะฐะฑะพัะฐััะธะต โ โค๏ธโ๐ฅะฒ ะขััะบะผะตะฝะธััะฐะฝะต ๐น๐ฒ ๐ฌัะฐั: @FULL_SERWERS_CHAT ะะปั ัะตะบะปะฐะผั: @Advert_chanell ะะฐะฝะฐะป ัะพะทะดะฐะฝ: 03.03.2024 ะณ ๐น๐ฒ |
| Created | Between 1 November 2023 and 31 May 2024 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 14 November 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 2 |
| On Telegram | t.me/FULL_SERWERS |
Other / unclassifiable โ a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channelโs own recent posts on 15 November 2026 and assigned it the closest of 31 fixed categories, at 53% 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 the other topics.
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 in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 26 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts 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 |
|---|---|---|---|
| @VPN_OrginalTm/6951863 Nov 2026, 14:44 UTC | @FULL_SERWERS/211371 ยท this entry15 Nov 2026, 15:27 UTC | 1.00 | 12 days |
| @VPN_OrginalTm/6952353 Nov 2026, 15:23 UTC | @FULL_SERWERS/210712 ยท this entry14 Nov 2026, 19:06 UTC | 1.00 | 11 days |
| @VPN_OrginalTm/6952373 Nov 2026, 15:23 UTC | @FULL_SERWERS/210713 ยท this entry14 Nov 2026, 19:06 UTC | 1.00 | 11 days |
| @VPN_OrginalTm/6952383 Nov 2026, 15:24 UTC | @FULL_SERWERS/210692 ยท this entry14 Nov 2026, 18:29 UTC | 1.00 | 11 days |
| @VPN_OrginalTm/6984085 Nov 2026, 15:39 UTC | @FULL_SERWERS/210734 ยท this entry14 Nov 2026, 19:40 UTC | 1.00 | 9 days |
| @VPN_OrginalTm/71106113 Nov 2026, 16:39 UTC | @FULL_SERWERS/210729 ยท this entry14 Nov 2026, 19:32 UTC | 1.00 | 27 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @VPN_OrginalTm | 7 (7/7 hand-verifiable sample passed) | 1.00 | 11 days | @VPN_OrginalTm (7โ0) |
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. 7 of the 7 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 27 comparable posts for this entry, running 6 October 2026 to 15 November 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.
Of the group of 26 channels, the one whose matching posts we hold earliest is @TM_VPN_KODLARY. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entryโs content came from. It is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 16 November 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 is in a group of 26 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. โFirstโ could only mean first in our own crawl, which depends on how deep we happened to reach into each channelโs history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a โForwarded fromโ credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.
4 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 13:22 | 17,149 | no change |
| 14 Nov 2026, 12:47 | 17,149 | first reading |
44 posts held, back to 30 September 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 6 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. It is computed over the 10 of 37 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days ยท latest post in window 16 November 2026 |
|---|---|
| Posts held | 44 (30 September 2026 โ 16 November 2026) |
| Views total | 19,059 |
| Reactions total | 178 |
| Forwards / comments | not exposed by the public surface โ not measured, not estimated |
| Readings taken | 16 Nov 2026, 03:42 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 16 November 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.
247 reactions across 15 posts, in 5 distinct kinds. The most used accounts for 70.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| โค | 175 | 70.9% | |
| ๐ | 69 | 27.9% | |
| โคโ๐ฅ | 1 | 0.405% | |
| ๐ | 1 | 0.405% | |
| ๐จโ๐ป | 1 | 0.405% |
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 15 of the 44 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 247 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 44 most recent posts we hold, published 30 September 2026 to 16 November 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.
Telegramโs own โeditedโ marker: 6 of 37 posts held from the last 30 days (16.2%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before โ this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Like basmagy unutman โค๏ธ
Signed Auto Post BOT
- ๐ณ๐๐๐๐๐พ๐๐๐๐๐บ๐๐๐ ๐๐ ๐ฆ๐๐๐ผ๐ ๐๐ ๐๐๐๐ ๐บ๐๐ ๐๐๐ ๐ป๐๐๐ฝ๐บ ๐ - ๐ฏ๐๐ป๐๐ฎ, ๐จ๐๐๐๐บ๐๐๐บ๐๐ฑ, ๐ณ๐๐๐ณ๐๐๐ฑ, ๐ธ๐๐๐๐๐ป๐พ๐ฑ,๐ผ๐ ๐บ๐๐ ๐๐ฟ ๐ผ๐ ๐บ๐๐โ๏ธ ๐๐พ ๐.๐ ๐ฑ ๐๐พ๐๐๐พ ๐๐๐๐พ๐๐๐พ๐ ๐๐ ๐บ๐๐ฟ๐๐๐๐บ๐ ๐บ๐๐ ๐๐ผ๐๐ ๐ก ๐จ๐ฎ๐ฒ ๐ฑ ๐ ๐ญ๐ฃ๐ฑ๐ฎ๐จ๐ฃ ๐ฑ ๐ฒ๐พ๐ ๐๐พ๐ ๐ต๐๐๐๐๐ ๐ช๐๐๐พ๐๐๐พ โ ๐ก๐๐ฝ๐บ ๐ช๐บ๐๐บ๐ ๐n๐๐๐ ๐๐ล๐ฝ๐๐๐๐บ๐ รผรง๐๐ ๐๐บ๐ป๐บ๐๐ ๐บ๐๐๐๐ ๐ฅ : @duydansyz
Signed ๏ฟถ ๏ฟด๏ฟด๏ฟด ๏ฟด๏ฟด ๏ฟถ ๏ฟถ๏ฟถ๏ฟถ๏ฟถ ๏ฟถ๏ฟถ๐ ๐ ๐ ๐ ๐
Like basalyล doslar kod iลlรคp dur โ๐ปโ
Signed โฒ ๊ฎ ๊ช โบ โฒ โฒ แฅฑ ๊ญฒ
โ๏ธ๐ฉ๐๐ฃ ๐ฉ๐๐๐ฆ๐ฆ & ๐ฆ๐๐๐๐ข๐ช๐ฆ๐ข๐๐๐ฆ ๐ธ๐ผ๐ฑ๐ ๐ฏ๐ผ๐ฑ๐ฎ ๐ด๐ผ๐๐๐น๐ฑ๐ ! ๐๐น๐ผ๐ฐ๐ธ ๐๐ฎ๐ด๐ฑ๐ฎ๐๐ ๐๐ผ๐ธ, ๐๐ถ๐๐น๐ถ๐ธ ๐๐น๐๐ฟ๐ฎ-๐๐ถ๐! ๐ก ๐ฎ ๐๐ฒ๐บ๐บ๐ฒ ๐๐ฎ๐ ๐ฑ๐ผ๐ป๐บ๐ฎ๐ป ๐ถ๐๐น๐ฒ๐๐ฎ๐ฟ: ๐ฌ๐ผ๐๐ง๐๐ฏ๐ฒ ๐ฅ โ 4๐ ๐ณ๐ผ๐ฟ๐บ๐ฎ๐๐ฑ๐ฎ ๐ฑ๐ผ๐ป๐บ๐ฎ๐ป ๐ด๐ผ๐ฟ๐ธ๐ฒ๐๐๐ฎ๐ฟ ๐ฟ โฆ ๐๐ก๐ฆ๐ง๐๐ ๐ง๐ง๐ฅ ๐ง๐๐ ๐ง๐ช๐๐ง๐๐๐บ โ ๐ง๐ถ๐๐น๐ถ๐ธ ๐บ๐ฎ๐ธ๐๐ถ๐บ๐๐บ โก๏ธ โฆ ๐ฃ๐จ๐๐ ๐ ๐ผ๐ฏ๐ถ๐น๐ฒ๐ฎ โ ๐ฃ๐ฒ๐ ๐ฃ๐๐ก๐ ๐ฏ๐ฒ๐ฟ๐๐ฎ ๐ฅ ๐ช๐๐ข๐ง๐ ๐๐๐ก๐๐ ๐๐๐ฌ๐๐ก ๐: ๐ @Decsikx ๐ป ๐จ๐ก๐ฆ ๐๐๐ฅ๐๐ก: ๐ ๐๐ด๐ ๐ธ๐ผ๐ฑ๐ ๐ฑ๐ถ๐ป๐ฒ ๐ถ๐น๐ธ๐ถ๐ป๐ท๐ถ 300 ๐ฎ๐ฑ๐ฎ๐บ ๐ฎ๐น๐๐ฝ ๐ฏ๐ถ๐น๐๐ฎ๐ฟ! ๐๐น๐๐ฝ ๐๐ฒ๐๐ถ๐๐ถ๐ป โฐ
Signed ๐ท๐๐๐๐๐ ๐
Like basmagy unutman โค๏ธ
Signed Auto Post BOT
happ://crypt5/fzvdGZ7sab9A15VPh7eeiCvc25cbY - Boda 1 Gรผnlik bez blok kod goyuldy โ - YouTube๐ฌInstagram๐ฑ - TikTok๐ฑyaryp acyaโ - 100 adam alyp bilya๐ - Bodun eyesi : @babo_org โ
Signed โฌะโญโฌะฐโญโฌะฑโญโฌะพโญ
Siz bu โ bot bilen tรคzeje รฝaryp duran happ we shadowsocks โ๏ธ kodyny alyp bilersiรฑiz ๐ IลLEรลI รARYP ATYLYP IลLEรร LรUBOร ZADAMAรรA TIKTOK๐น INSTAGRAM๐ท YOUTUBE๐น TELEGRAMโ๏ธ KODY ALMAK รรIN AลAKDAKY โ๏ธ KNOPKALARYร BIRINI BASYP ULANYBERIร BODA KANAL ALรAN รAZ: @zonex015
Signed ๐๐๐๐๐ฟ VPN
- ๐ณ๐๐๐๐๐พ๐๐๐๐๐บ๐๐๐ ๐๐ ๐ฆ๐๐๐ผ๐ ๐๐ ๐๐๐๐ ๐บ๐๐ ๐๐๐ ๐ป๐๐๐ฝ๐บ ๐ - ๐ฏ๐๐ป๐๐ฎ, ๐จ๐๐๐๐บ๐๐๐บ๐๐ฑ, ๐ณ๐๐๐ณ๐๐๐ฑ, ๐ธ๐๐๐๐๐ป๐พ๐ฑ,๐ผ๐ ๐บ๐๐ ๐๐ฟ ๐ผ๐ ๐บ๐๐โ๏ธ ๐๐พ ๐.๐ ๐ฑ ๐๐พ๐๐๐พ ๐๐๐๐พ๐๐๐พ๐ ๐๐ ๐บ๐๐ฟ๐๐๐๐บ๐ ๐บ๐๐ ๐๐ผ๐๐ ๐ก ๐จ๐ฎ๐ฒ ๐ฑ ๐ ๐ญ๐ฃ๐ฑ๐ฎ๐จ๐ฃ ๐ฑ ๐ฒ๐พ๐ ๐๐พ๐ ๐ต๐๐๐๐๐ ๐ช๐๐๐พ๐๐๐พ โ ๐ก๐๐ฝ๐บ ๐ช๐บ๐๐บ๐ ๐n๐๐๐ ๐๐ล๐ฝ๐๐๐๐บ๐ รผรง๐๐ ๐๐บ๐ป๐บ๐๐ ๐บ๐๐๐๐ ๐ฅ : @duydansyz
Signed ๏ฟถ ๏ฟด๏ฟด๏ฟด ๏ฟด๏ฟด ๏ฟถ ๏ฟถ๏ฟถ๏ฟถ๏ฟถ ๏ฟถ๏ฟถ๐ ๐ ๐ ๐ ๐
Like sany juda az๐๐
Signed โฒ ๊ฎ ๊ช โบ โฒ โฒ แฅฑ ๊ญฒ
happ://crypt5/fzvdbh9FKjuE2OS9RRVppqM428Xk9y8LWdz/5IF1tcaudnCYQGabAe4yL0mezyfx8PVVmF7ZhBDtPSXMPzNYW4anWQgo92PEtyHRvEKCpW/8ptz6BAbGC+U3on7loaCZb6wx0GklE21P1lGa8RFVzKDDnKTRmF95uXd+RhC+68hfEFlHQKKmcMr05Iq8FkmP8qHsoqby8JFDOPjhjLNgav7CA3H4QhId5ucV0yAfbgWwxqj/DV1/tfB6alEr4JLAKo6yZ0nSbI6JCcrgb/vUr8zZkrrxV87jY9JwVAy2vPoYbpHlVEIkLboDPJ526BQi7mMwJBek6zCmlvzYhx7DqA1RIuFzRFzREfkAYXW5+/WLcIoEDUpxa1gMP2JhKQlHMazhlMuIy1WPNLsPtSMBFXโฆ
โค5๐2
Signed ๐๐ฒ๐๐ด๐ฎ๐๐ฒ โก
Like basmagy unutman โค๏ธ
Signed Auto Post BOT
Like basmagy unutman โค๏ธ
Signed Auto Post BOT
Showing the 12 most recent of 44 posts we hold for @FULL_SERWERS. 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.
@FULL_SERWERS edited 1 post 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.
We recorded 3 posts on @FULL_SERWERS as deleted โ posts this register held that were missing from the channelโs public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channelโs public page, and when โ not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 14 November 2026 โ this entry's latest reading, not the date you are reading this.
โ๐๐๐ ๐๐๐๐๐๐๐๐๐๐๐๐๐โ (@FULL_SERWERS), 17,149 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/FULL_SERWERS.
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.