Telegram RegisterThe public register of Telegram
Telegram profile photo for TrackANaziMerc

Channel

TrackANaziMerc

@TrackAMerc

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Referenced elsewhere · Cite this entry

81,466subscribers

+8,056 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001700385921
TypeChannel
Username@TrackAMerc
DescriptionTracking Nazis and mercenaries in Ukraine and more Сhat https://t.me/TrackAMercChat
Created18 September 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live9 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/TrackAMerc

Topic

International news — 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 20 August 2026 and assigned it the closest of 31 fixed categories, at 68% 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.

Observations

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.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. 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.

Matching posts — open both and compare (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@TrackAMerc/15498 · this entry14 Sept 2026, 11:01 UTC@Slavyangrad/17775017 Sept 2026, 19:45 UTC1.003 days
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@Slavyangrad5 (5/5 hand-verifiable sample passed)1.0026 hoursthis entry (5–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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 126 comparable posts for this entry, running 2 August 2026 to 10 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_source, 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.

Growth

73,41081,52377,466.581,4666 August 20269 November 2026
63 measurements spanning 96 days, net +8,056. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 72,193–82,740 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
9 Nov 2026, 23:0681,466-28
8 Nov 2026, 16:5981,494-22
7 Nov 2026, 12:1581,516+6
6 Nov 2026, 10:1981,510+4
5 Nov 2026, 07:1481,506-17
3 Nov 2026, 05:1081,523+63
2 Nov 2026, 04:0181,460+96
1 Nov 2026, 00:2181,364+6
30 Oct 2026, 23:1981,358+51
29 Oct 2026, 21:0681,307+99
28 Oct 2026, 19:0881,208+48
27 Oct 2026, 20:1781,160-21
26 Oct 2026, 18:4181,181+52
25 Oct 2026, 22:0581,129+12
24 Oct 2026, 22:1681,117-18
23 Oct 2026, 21:3181,135-13
22 Oct 2026, 22:1781,148+78
21 Oct 2026, 22:5481,070+95
20 Oct 2026, 16:5980,975+34
19 Oct 2026, 17:3080,941first reading

Engagement

127 posts held, back to 2 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 194 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
15.5%
avg views ÷ 81,466 subscribers
Avg views / post
12,600
35 posts measured
Reaction rate
2.58%
reactions ÷ views · ER floor
Posts in window
35
of 127 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 November 2026
Posts held127 (2 August 2026 – 10 November 2026)
Views total441,080
Reactions total11,383
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Nov 2026, 19:19 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.

What this channel posts

Photos
≈14,800
Videos
≈413
Links
≈2,790

Lifetime counters from Telegram’s own channel header, read 10 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.

Video runtime
24m 54s
Average length
1m 28s

Measured directly from 17 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.

Reaction mix

40,228 reactions across 124 posts, in 34 distinct kinds. The most used accounts for 28.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 545616412454945425711,46228.5%
💩6,39415.9%
🎉4,86812.1%
custom 50892518502055298734,85212.1%
🍾4,30610.7%
❤2,7576.85%
👍2,4176.01%
🔥7381.83%
🤬4291.07%
🖕3920.974%
🤣3150.783%
🤡2060.512%
😁1660.413%
🕊1470.365%
🦄1390.346%
🌭1030.256%
🤪830.206%
👻810.201%
👏680.169%
🍌560.139%
14 further kinds2490.619%

Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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 127 of the 127 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 41,241 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 127 most recent posts we hold, published 2 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 Stars

Stars received
441
across the posts below
Posts paid on
31
of 127 we hold a reading for · 24%
Most on one post
251
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @TrackAMerc. 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 127 most recent posts we hold for this entry, published 2 August 2026 to 10 November 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 35 posts held from the last 30 days (0%) 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 Nov 2026, 07:04 UTC≈4,630 views158 reactions1 Starread 10 November 2026
Photo

Gilson Junio Ramos Matias from Ipaba, Minas Gerais, Brazil IG, FB (ID 73786476237, 100095437984350) Jeferson Araujo de Oliveira from Parnamirim, Rio Grande do Norte, Brazil IG, FB (ID 13689501644, 100001414180209) Raphael Lemos Guimarães from Araruama, Rio de Janeiro, Brazil IG, FB, TK (ID 64771861464, 61556629360117, 7101731011227321350) Edson Jose da Costa Almeida from Batayporã, Mato Grosso do Sul, but lives…

custom 545616412454945425777💩39custom 508925185020552987317❤10🦄7👍3🤬2🍾1

9 Nov 2026, 07:02 UTC≈8,120 views241 reactionsread 10 November 2026
Photo

Erik Antero da Silva from Brejo da Madre de Deus, but lives in Santa Cruz Do Capibaribe, Pernambuco, Brazil IG, IG, FB (ID 78888592896, 3507550409, 100006511934847) Cirineu de Sousa Coutinho from Corda, Maranhão, Brazil IG (ID 37343324111) Lucas Moreira dos Santos from Bauru, São Paulo, Brazil IG, FB (ID 4483713064, 100040862894226) Leandro Pimentel Couto from Uberlandia, Minas Gerais, Brazil IG, IG, FB (ID 72…

💩107custom 545616412454945425769custom 508925185020552987326❤18👍7🦄5🖕3🤬3

8 Nov 2026, 07:04 UTC≈9,930 views254 reactionsread 10 November 2026
Photo

Eliel Ganassoli da Rosa from Marabá, Pará, Brazil IG, FB (ID 53288605422, 100063935743917) Cleberson Veneziano Junior da Silva from Porto Velho, Roraima, Brazil FB, IG (ID 100004006731015, 262589876) Lucas Diniz Rodrigues from Curvelo, Minas Gerais, Brazil IG, FB, FB (ID 6254259720, 100003658408339, 100023854419000) Marcelo Alves Barcelos from Carazinho, Rio Grande do Sul, Brazil TK, TK, IG, FB, LK (ID 6813667…

💩111custom 545616412454945425771custom 508925185020552987326❤23👍9🍾4🤬4🖕3

7 Nov 2026, 07:01 UTC≈11,400 views268 reactionsread 10 November 2026
Photo

Alexandre Brito e Silva from Vitória da Conquista, Bahia, Brazil IG (ID 15021551824) Patrick da Silva Rios callsign Sagat from Rio de Janeiro, Brazil IG, FB (ID 11593236137, 100014893929891) Marcelo Galvão dos Santos from Nova Venécia, Espirito Santo, Brazil IG, FB, TK (ID 5488318637, 100011967991782, 6811476737597211654) Gabriel Maquiné dos Santos from Manaus, Amazonas, Brazil IG (ID 77920510122) Felipe Cost…

custom 5456164124549454257131💩71custom 508925185020552987330❤19👍6🏆3🤬3🍾2

6 Nov 2026, 07:04 UTC≈11,600 views292 reactionsread 9 November 2026
Photo

Fabio Ribeiro de Araujo callsign Rocco from Rio de Janeiro, Brazil IG, FB (ID 309584113, 100000294512840) Gabriel Italo dos Santos Silva from Brasilia, Brazil IG (ID 73515685650) Steven dos Santos Rodrigues callsign Pastor from Viana, Espirito Santo, Brazil IG, FB, LK (ID 4337908638, 100001034391842) Vinicios Santos do Carmo callsign Do Carmo from Brasilia, Brazil IG (ID 4126092083) Lucca Alexandre from Serra…

custom 5456164124549454257128custom 508925185020552987362💩56❤21👍6🤬6🏆4🖕4

5 Nov 2026, 07:04 UTC≈11,700 views320 reactionsread 8 November 2026
Photo

Maria Francine Gavlik Rocha from Itapema, Santa Catarina, Brazil IG, FB (51915649582, 100077675214326) Thiago Morais da Silva Moita callsign Badboy from São Gonçalo, Rio de Janeiro, Brazi FB, IG (ID 100000981515179, 77707470508) Rosquildes Bispo dos Santos Filho from Salvador, Bahia, Brazil IG, IG, IG, FB, FB, FB, TK (ID 76287041791, 1464226292, 76745564936, 61580018570187, 61583784674589, 1800220492, 7497232496…

💩142custom 545616412454945425797custom 508925185020552987333❤24🖕5🍾4👍4🤬4

4 Nov 2026, 07:02 UTC≈11,900 views276 reactionsread 7 November 2026
Photo

Bruno Mendes de Bessa from Frutal, Minas Gerais, Brazil IG, FB (ID 49401801683, 100000389190330) Igor de Jesus da Cunha Bezerra from Castanhal, Pará, Brazil TK, TK, FB, IG (ID 6812021693654123526, 7566037814846145547, 100013623222085, 6968965558) Marcello Paixão Dias from Belém, Pará, but lives in Florianópolis, Santa Catarina, Brazil IG, IG, FB, FB (ID 47866218641, 9776830916, 100093153614541, 100027746115520) …

custom 5456164124549454257129💩70custom 508925185020552987331❤21👍6🖕5🍾4🤬4

3 Nov 2026, 07:04 UTC≈12,100 views289 reactionsread 6 November 2026
Photo

Leonardo Batista Guiomar callsign Guiomar from Macapá, Amapá, Brazil TK, IG, IG, FB, FB, FB, FB (ID 7354903117013894149, 18929879985, 26252276741, 100021988278728, 61552145265411, 100009289989182, 100039312170037) Bryan Rodrigo Lopes Azevedo from Goiânia, Goiás, Brazil FB, IG (ID 100005084641133, 7609759427) Marcos Vinicius de França dos Santos from Estrela de Alagoas, Alagoas, Brazil IG (ID 46881774832) Jafe B…

💩122custom 545616412454945425774custom 508925185020552987344❤23👍10🤬5🖕3🦄3

2 Nov 2026, 07:00 UTC≈12,400 views286 reactionsread 5 November 2026
Photo

Vitor Santos callsign Titã from Marabá, Pará, Brazil IG, FB (ID 47647515378, 100067417450188) Anderson Daniel Rodrigues Ferreira from Campinas, Sao Paulo, Brazil IG, FB (ID 1496880766, 100002374266137) Jose Antonio Garcia Neto from Piracicaba, São Paulo, Brazil IG, FB (ID 373193043, 100000440098326) Pedro Luiz Amaro de Almeida from Cachoeiro de Itapemirim, Espírito Santo, but lives in São Paulo, Brazil IG, FB, …

💩129custom 545616412454945425779custom 508925185020552987332❤19👍10🤬6🍾4🦄3

1 Nov 2026, 07:02 UTC≈13,200 views271 reactionsread 5 November 2026
Photo

Francisco Ruz Ortiz Cervantes from Colombia TK, FB, IG (ID 7268022025061942278, 61568952431715, 51081197135) Miguel Angel Ibarra Alarcon from Caparrapí, Cundinamarca, Colombia TK, TK, FB, IG (ID 7433552184661001222, 7168273911543841797, 100011738086854, 5628694118) Andres Manuel Velasquez Rocha from Colombia TK, IG, FB (ID 6911171098130777093, 61250639206, 100002366530348) Miguel Antonio Medina Ruiz from Bogotá…

custom 5456164124549454257146💩66custom 508925185020552987327❤11👍7🤬5🍾3🖕3

31 Oct 2026, 07:02 UTC≈12,800 views274 reactionsread 4 November 2026
Photo

Estarlin Gonzalez Garcia callsign Maradona from Santiago de Cali, Valle del Cauca, Colombia TK, TK, TK, IG, FB (ID 7600840254401397781, 7327138281689547781, 7052404525232063489, 27980344180, 61590669562494) Ari David Jerez Vega callsign Aguila from Cartagena, Bolivar, Colombia TK, FB, IG (ID 6902010624084771845, 100010160718309, 9418977414) Juan Camilo Triana Serrano callsign Antmax from Cúcuta, Norte de Santande…

custom 5456164124549454257142💩59custom 508925185020552987334❤14👍8🖕7🤬4🍾3

30 Oct 2026, 03:01 UTC≈13,800 views474 reactions1 Starread 3 November 2026
Photo

Foreign mercs down! They all came to fight Russia and lost The Khartia Brigade has fallen into a cycle of sending new soldiers to the Kupyansk front and losing them. For every 100 killed, there’s a propaganda video in which they claim to have captured 500 meters of some empty forest. The work of our brothers from the 27th Separate Guards Motor Rifle Brigade, 1st Guards Tank Army, Western Military District, and the…

🎉240custom 545616412454945425769🍾65❤34custom 508925185020552987329👍21🕊7🔥3

Showing the 12 most recent of 127 posts we hold for @TrackAMerc. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

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.

Mentions

Named by 59 registered channels — 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Wikipedia

2 Wikipedia articles name this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.

Martin Mycielski (en.wikipedia.org)
“…web |title=Martin Mycielski from Poland, Lives in Brussels. |url=https://t.me/TrackAMerc/3758 |website=TrackANaziMerc |access-date=2 July 2026}}…”
read 1 November 2026
Марчін Мичельський (uk.wikipedia.org)
“…у допомозі Україні.{{cite web |title=Марчин Мычельский |url=https://t.me/TrackAMerc/3758 |website=TrackANaziMerc |date=лютий 2023 |language=ru |access-date=30…”
read 1 November 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 9 November 2026 — this entry's latest reading, not the date you are reading this.

“TrackANaziMerc” (@TrackAMerc), 81,466 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/TrackAMerc.

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.