10.11.2026 Germany ๐ฉ๐ช Searches at Hansa Rostock this morning. 16 apartments. 1312
๐247๐12๐ 8โค7๐4

Channel
@Gruppa_OF
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 ยท Polls ยท Citations ยท Telegram's recommendations ยท Cite this entry
183,046subscribers
+1,177 since we began measuring on 6 August 2026
Risers and fallers across the register ยท movement among entries of 100,000โ316,228.
| Telegram ID | -1001484150043 |
|---|---|
| Type | Channel |
| Username | @Gruppa_OF |
| Description | # ๐ ๐ณ๐๐๐๐๐๐๐ ๐๐๐๐ ๐๐๐๐๐ ๐๐ ๐๐๐๐๐ ๐ ๐ ข๐ ฃ. โทโฟโฟโน ๐๐ ๐๐ ๐๐๐ก ๐๐๐๐๐๐๐๐ก๐ ๐ค๐๐กโ ๐๐๐ข๐๐๐๐๐๐ ๐ก๐ ๐๐๐ ๐๐๐โ๐๐๐๐ก ๐กโ๐ ๐๐ข๐๐๐๐๐๐ก๐๐๐ ๐๐ ๐๐๐๐๐๐๐๐ก๐๐๐ send us messages to @GruppaOFbot |
| Created | 4 September 2019 โ measured โ cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/Gruppa_OF |
Sports โ 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 93% 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 forms a group of 2 channels linked by matching posts. 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 |
|---|---|---|---|
| @GruppaOF_arrangefight/81031 Oct 2026, 18:30 UTC | @Gruppa_OF/39417 ยท this entry31 Oct 2026, 18:30 UTC | 1.00 | under a minute |
| @GruppaOF_arrangefight/81231 Oct 2026, 20:04 UTC | @Gruppa_OF/39423 ยท this entry31 Oct 2026, 20:04 UTC | 1.00 | under a minute |
| @GruppaOF_arrangefight/8211 Nov 2026, 15:11 UTC | @Gruppa_OF/39443 ยท this entry1 Nov 2026, 15:11 UTC | 1.00 | under a minute |
| @GruppaOF_arrangefight/8232 Nov 2026, 06:55 UTC | @Gruppa_OF/39546 ยท this entry4 Nov 2026, 18:21 UTC | 1.00 | 2 days |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @GruppaOF_arrangefight | 20 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @GruppaOF_arrangefight (18โ2) |
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. 9 of the 9 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 227 comparable posts for this entry, running 4 August 2026 to 9 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 2 channels, the one whose matching posts we hold earliest is @GruppaOF_arrangefight. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 11 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 2 registered channels linked by matching posts. 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 08:55 | 183,046 | -57 |
| 9 Nov 2026, 13:11 | 183,103 | -38 |
| 8 Nov 2026, 07:16 | 183,141 | -17 |
| 7 Nov 2026, 03:07 | 183,158 | -27 |
| 6 Nov 2026, 03:26 | 183,185 | -8 |
| 5 Nov 2026, 04:08 | 183,193 | -19 |
| 3 Nov 2026, 09:29 | 183,212 | -16 |
| 2 Nov 2026, 11:46 | 183,228 | +5 |
| 1 Nov 2026, 14:38 | 183,223 | -14 |
| 31 Oct 2026, 13:01 | 183,237 | -23 |
| 30 Oct 2026, 09:59 | 183,260 | -50 |
| 29 Oct 2026, 07:10 | 183,310 | -42 |
| 28 Oct 2026, 05:59 | 183,352 | -45 |
| 27 Oct 2026, 05:10 | 183,397 | -12 |
| 26 Oct 2026, 08:26 | 183,409 | +114 |
| 25 Oct 2026, 05:16 | 183,295 | +46 |
| 24 Oct 2026, 04:55 | 183,249 | -42 |
| 23 Oct 2026, 02:40 | 183,291 | +32 |
| 22 Oct 2026, 05:07 | 183,259 | +49 |
| 21 Oct 2026, 01:21 | 183,210 | first reading |
999 posts held, back to 4 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 201 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 348 of 350 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days ยท latest post in window 10 November 2026 |
|---|---|
| Posts held | 999 (4 August 2026 โ 10 November 2026) |
| Views total | 5,882,281 |
| Reactions total | 34,982 |
| Forwards / comments | not exposed by the public surface โ not measured, not estimated |
| Readings taken | 11 Nov 2026, 19:00 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 11 November 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 603 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.
98,844 reactions across 997 posts, in 17 distinct kinds. The most used accounts for 31.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ๐ฅ | 30,645 | 31.0% | |
| ๐ | 18,275 | 18.5% | |
| โค | 17,738 | 17.9% | |
| ๐ | 10,342 | 10.5% | |
| ๐ | 9,913 | 10.0% | |
| ๐ | 4,221 | 4.27% | |
| ๐ | 3,301 | 3.34% | |
| ๐ | 1,281 | 1.30% | |
| ๐ | 1,088 | 1.10% | |
| โก | 552 | 0.558% | |
| ๐ฑ | 397 | 0.402% | |
| ๐ซก | 318 | 0.322% | |
| ๐ | 255 | 0.258% | |
| ๐ค | 179 | 0.181% | |
| ๐ | 173 | 0.175% | |
| ๐ฏ | 101 | 0.102% | |
| ๐ | 65 | 0.066% |
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 997 of the 999 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 98,844 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 999 most recent posts we hold, published 4 August 2026 to 10 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: 90 of 350 posts held from the last 30 days (25.7%) 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).
10.11.2026 Germany ๐ฉ๐ช Searches at Hansa Rostock this morning. 16 apartments. 1312
๐247๐12๐ 8โค7๐4
07.11.2026 Germany๐ฉ๐ช 3 league Aachen before the match against Rot-Weiss Essen
๐ฅ56โค9๐9๐5๐5๐1
08.11.2026 Portugal๐ต๐นVitรณria - Porto. White Angels (Vitรณria SC) pyro-show PYRO https://t.me/PyroGruppaOF
๐ฅ44๐11๐4โค1๐1
08.11.2026 Denmark๐ฉ๐ฐ derby Copenhagen. Brรธndby yesterday against FC Kรธbenhavn
๐ฅ67๐6๐ซก5๐4โค3
XX.11.2026 Czech๐จ๐ฟArrange fight. Pardubickรก Omladina (Pardubice) vs Warriors (Teplice). 5ร5. 1 min. Win. Pardubice๐ธ
๐14๐ฅ9๐4๐3
06.11.2026 Sweden๐ธ๐ช Hammarby at home against Elfsborg
๐ฅ35๐7โค1๐ซก1
08.11.2026 Portugal ๐ต๐น Pyro-show ultras Porto against Vitรณria
๐ฅ40๐18๐5๐3โค1๐1๐ฑ1
08.11.2026 Italy ๐ฎ๐น Fiorentina last night against Juventus
๐ฅ50โค16๐11๐5๐4๐3
08.11.2026 Denmark ๐ฉ๐ฐ Horsens stolen flag Viborg Info Viborg: Thatโs not how it happened at all, itโs actually a flag we left behind during an away trip to Aarhus (AGF) the last time we played against them.
๐31๐ฅ8๐4โค1๐1
08.11.2026 Netherlands ๐ณ๐ฑ GHC (Groningen) in Alkmaar yesterday. Alkmaar no show
๐ฅ38๐11โค5๐ฏ5๐5
08.11.2026 Germany๐ฉ๐ช 4 league. Lokomotive Leipzig against Zwickau
๐ฅ63๐11โค9๐1
08.11.2026 Germany ๐ฉ๐ช Hoffenheim against Schalke 04
๐92๐14๐12๐ฅ5๐4โค2
Showing the 12 most recent of 999 posts we hold for @Gruppa_OF. 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.
@Gruppa_OF edited 5 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.
We recorded 4 posts on @Gruppa_OF 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A pollโs figures keep moving after that, so each one is dated.
๐ช๐ต๐ผ ๐๐๐ผ๐น๐ฒ ๐๐ต๐ฒ ๐ฏ๐ฎ๐ป๐ป๐ฒ๐ฟ๐ ๐ณ๐ฟ๐ผ๐บ ๐ฅ๐ฎ๐ฝ๐ถ๐ฑ ๐ช๐ถ๐ฒ๐ป๐ฆ๐น?
The shares total 105%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not 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 999 most recent posts we hold, published 4 August 2026 to 10 November 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.
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 10 September 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.
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 11 November 2026 โ this entry's latest reading, not the date you are reading this.
โ๐๐ซ๐ฎ๐ฉ๐ฉ๐๐๐ ๐ณ ๐๐๐๐ข๐๐ข๐๐ฅโ (@Gruppa_OF), 183,046 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/Gruppa_OF.
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.