Engagement
7 posts held, back to 21 August 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
- 233.1%
- avg views ÷ 37 subscribers
- Avg views / post
- 86.3
- 4 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 4
- of 7 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.
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
29 Jul 2026, 17:33 UTC63 viewsread 10 August 2026 Forwarded from @HateslavPhoto
"𝐑𝐞𝐩𝐨𝐫𝐭 𝐭𝐨 𝐎𝐐𝐮 𝐈 [Oberquartiermeister I; First Deputy Chief of the General Staff] regarding the Admiral's [Canaris] assignment. Sends me immediately to Chef d. Genstb. [Chef des Generalstabes; Chief of the General Staff]. He says that the butcheries by the Poles behind the front are indeed increasing to such an extent that rigorous intervention will probably soon be necessary. He says it is the intention of the Führe…
29 Jul 2026, 16:38 UTC91 viewsread 10 August 2026 Photo
"III B 2 d - Dr. Str. /Sun. Berlin, October 18, 1944
Re: Reorganization of Poland policy
The Polish policy, which has been represented since 1939, was based on the following four requirements:
1.) the thousand-year struggle between the German and Polish people, the Polish war guilt and the murder of tens of thousands of ethnic Germans in September 1939.
2.) the biological inferiority of most of the Polish people an…
29 Jul 2026, 08:52 UTC112 viewsread 10 August 2026 Racial policy in the poland:
"I received your letter dated March 9, 1942. I absolutely agree with your thoughts that abortion should not be punished among Polish women. I wrote to the senior and police leader, Obergruppenführer Krüger with this in mind."
— Heinrich Himmler, BArch NS 19/3438 p.3
The selection of the population will be carried out by the chief of the security police in agreement with SS Obergruppenfu¨h…
28 Jul 2026, 19:41 UTC79 viewsread 10 August 2026 Photo
Lieutenant General Bock of the German army gave a policy assessment report to the Reich Governor and Gauleiter on the situation in Poland:
"It must not be overlooked that, apart from the necessary harsh measures of expropriation and resettlement, the Poles are being driven to a state of despair by the closure of churches, the shooting of priests, the destruction of holy images before their very eyes, the constant th…
18 Jul 2026, 10:35 UTC624 viewsread 10 August 2026 Photo
𝐓𝐡𝐞 𝐒𝐒 𝐮𝐬𝐢𝐧𝐠 𝐏𝐨𝐥𝐞𝐬 𝐚𝐬 𝐚𝐧 𝐚𝐧𝐚𝐥𝐨𝐠𝐲 𝐟𝐨𝐫 𝐠𝐞𝐧𝐞𝐭𝐢𝐜 𝐝𝐢𝐬𝐨𝐫𝐝𝐞𝐫𝐬
"Furthermore, in a one-hour lecture to the entire squadron, the training officer, standing in for the ailing squadron commander, discussed the artwork "Victory of the Weapons - Victory of the Child," which had been distributed to every squadron member. Using this excellent visual material, the SS members were shown that increased genetically healthy offspring we…
17 Jul 2026, 17:22 UTC126 viewsread 10 August 2026 Forwarded from @HateslavPhoto
𝐎𝐫𝐝𝐞𝐫𝐬 𝐟𝐫𝐨𝐦 𝐭𝐡𝐞 𝐏𝐫𝐞𝐬𝐬 𝐂𝐨𝐧𝐟𝐞𝐫𝐞𝐧𝐜𝐞 𝐨𝐟 𝐎𝐜𝐭𝐨𝐛𝐞𝐫 𝟐𝟒, 𝟏𝟗𝟑𝟗.
Directive No. 1306
"Regarding the treatment of the Polish question, the following applies: Detailed reports on the treatment of the Poles by the German occupation authorities are undesirable. All reports must stand under the leitmotif: Establishment of order, elimination of the chaotic state of affairs that the Polish state had brought about in all areas. It must…
Channel created
Showing the 7 most recent of 7 posts we hold for @polacksandthereich. 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.
Citation-graph rank
Citation-graph rank — 600,174 of 1,481,306entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
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.
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.
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 10 August 2026 — this
entry's latest reading, not the date you are reading this.
“Poles & the Reich Exposed” (@polacksandthereich), 37 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/polacksandthereich.
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.
