Trump, Belarus and ATOM ☝️ https://boostyfi.com/collective-purchase/3a75aa60-b7e4-44b3-b688-29fdd9f8604c?brand=satqm/?ref=philgodlewski
👍309🔥226❤201💯170🎉163

Channel
@philgodlewskii4
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Posts · Posts edited after publishing · Polls · Citations · Handles named that no longer answer · Domains linked from posts · Cite this entry
2,032,126subscribers
-11,524 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1003004997693 |
|---|---|
| Type | Channel |
| Username | @philgodlewskii4 |
| Created | 11 September 2025 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/philgodlewskii4 |
Other / unclassifiable — 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 72% 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 why it has no browse page of its own yet.
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 word for word on 3 other registered channels. They sit inside a group of 5 channels that share the same post bodies 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 |
|---|---|---|---|
| @atom_venture/8017 Jul 2026, 14:09 UTC | @philgodlewskii4/2533 · this entry17 Jul 2026, 14:19 UTC | 1.00 | 10 minutes |
| @atom_venture/8218 Jul 2026, 23:58 UTC | @philgodlewskii4/2551 · this entry19 Jul 2026, 00:01 UTC | 1.00 | 3 minutes |
| @atom_venture/8321 Jul 2026, 16:49 UTC | @philgodlewskii4/2568 · this entry21 Jul 2026, 16:50 UTC | 1.00 | 2 minutes |
| @atom_venture/8421 Jul 2026, 20:59 UTC | @philgodlewskii4/2572 · this entry21 Jul 2026, 23:07 UTC | 1.00 | 2.1 hours |
| @atom_venture/8523 Jul 2026, 17:47 UTC | @philgodlewskii4/2593 · this entry23 Jul 2026, 17:49 UTC | 1.00 | 2 minutes |
| @atom_venture/8926 Jul 2026, 13:26 UTC | @philgodlewskii4/2618 · this entry26 Jul 2026, 13:31 UTC | 1.00 | 4 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @atom_venture | 18 (8/8 hand-verifiable sample passed) | 1.00 | 7 minutes | @atom_venture (18–0) |
| @jggl_official | 13 (8/8 hand-verifiable sample passed) | 1.00 | 31 minutes | @jggl_official (11–2) |
| @Gin7erB | 9 (8/8 hand-verifiable sample passed) | 1.00 | 2.2 hours | this entry (9–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 25 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 940 comparable posts for this entry, running 5 February 2026 to 8 August 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.
Across the whole group of 5, the earliest publisher we hold is @jggl_official. That is a statement about our reading window, not a claim of authorship.
On 177 of the 211 posts we watched over 30 days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0076 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /286329 Aug 2026, 13:04 UTC | 35 minutes | 10,700 → 13,500at least +2,700 | 927 → 931at most +5 | +20.6 |
| /286329 Aug 2026, 13:04 UTC | 34 minutes | 21,000 → 25,600at least +4,500 | 945 → 948at most +4 | +34.3 |
| /286329 Aug 2026, 13:04 UTC | 30 minutes | 25,600 → 31,200at least +5,500 | 948 → 953at most +6 | +41.9 |
| /286329 Aug 2026, 13:04 UTC | 35 minutes | 31,200 → 36,700at least +5,400 | 953 → 958at most +6 | +41.1 |
| /286329 Aug 2026, 13:04 UTC | 35 minutes | 36,700 → 43,400at least +6,600 | 958 → 962at most +5 | +50.3 |
| /286329 Aug 2026, 13:04 UTC | 35 minutes | 48,500 → 63,600at least +15,000 | 965 → 969at most +5 | +114.3 |
| /286329 Aug 2026, 13:04 UTC | 35 minutes | 63,600 → 74,000at least +10,300 | 969 → 972at most +4 | +78.5 |
| /304511 Sept 2026, 12:21 UTC | 34 minutes | 20,000 → 25,500at least +5,400 | 879 → 888at most +10 | +41.1 |
| /304511 Sept 2026, 12:21 UTC | 35 minutes | 25,500 → 30,400at least +4,800 | 888 → 896at most +9 | +36.6 |
| /304511 Sept 2026, 12:21 UTC | 34 minutes | 30,400 → 38,200at least +7,700 | 896 → 901at most +6 | +58.6 |
| /304511 Sept 2026, 12:21 UTC | 35 minutes | 52,200 → 64,300at least +12,000 | 918 → 921at most +4 | +91.4 |
| /304511 Sept 2026, 12:21 UTC | 34 minutes | 69,400 → 80,600at least +11,100 | 924 → 928at most +5 | +84.5 |
| /304511 Sept 2026, 12:21 UTC | 35 minutes | 80,600 → 97,700at least +17,000 | 928 → 932at most +5 | +129.5 |
| /306913 Sept 2026, 12:03 UTC | 30 minutes | 15,900 → 23,400at least +7,400 | 896 → 904at most +9 | +56.4 |
| /306913 Sept 2026, 12:03 UTC | 33 minutes | 25,300 → 34,000at least +8,600 | 909 → 916at most +8 | +65.5 |
| /306913 Sept 2026, 12:03 UTC | 35 minutes | 36,400 → 45,500at least +9,000 | 920 → 922at most +3 | +68.6 |
| /306913 Sept 2026, 12:03 UTC | 33 minutes | 45,500 → 52,800at least +7,200 | 922 → 928at most +7 | +54.8 |
| /306913 Sept 2026, 12:03 UTC | 29 minutes | 52,800 → 62,600at least +9,700 | 928 → 934at most +7 | +73.9 |
| /306913 Sept 2026, 12:03 UTC | 37 minutes | 62,600 → 74,700at least +12,000 | 934 → 938at most +5 | +91.4 |
| /309416 Sept 2026, 20:29 UTC | 35 minutes | 20,200 → 27,300at least +7,000 | 917 → 924at most +8 | +53.3 |
| /309416 Sept 2026, 20:29 UTC | 30 minutes | 27,300 → 34,400at least +7,000 | 924 → 936at most +13 | +53.3 |
| /309416 Sept 2026, 20:29 UTC | 35 minutes | 34,400 → 43,100at least +8,600 | 936 → 946at most +11 | +65.5 |
| /309416 Sept 2026, 20:29 UTC | 30 minutes | 43,100 → 51,200at least +8,000 | 946 → 951at most +6 | +60.9 |
| /309416 Sept 2026, 20:29 UTC | 35 minutes | 51,200 → 73,500at least +22,200 | 951 → 958at most +8 | +169.1 |
| /309416 Sept 2026, 20:29 UTC | 35 minutes | 73,500 → 105,000at least +30,500 | 958 → 965at most +8 | +232.3 |
| /310519 Sept 2026, 14:37 UTC | 30 minutes | 16,400 → 23,200at least +6,700 | 866 → 877at most +12 | +51.0 |
| /310519 Sept 2026, 14:37 UTC | 35 minutes | 23,200 → 32,600at least +9,300 | 877 → 882at most +6 | +70.8 |
| /310519 Sept 2026, 14:37 UTC | 35 minutes | 32,600 → 39,900at least +7,200 | 882 → 886at most +5 | +54.8 |
| /310519 Sept 2026, 14:37 UTC | 6.3 hours | 39,900 → 98,000at least +58,000 | 886 → 936at most +51 | +441.8 |
| /310519 Sept 2026, 14:37 UTC | 73 minutes | 98,000 → 116,000at least +17,000 | 936 → 938at most +3 | +129.5 |
| /310519 Sept 2026, 14:37 UTC | 12 hours | 116,000 → 149,000at least +32,000 | 938 → 973at most +36 | +243.7 |
| /285527 Aug 2026, 14:37 UTC | 30 minutes | 23,400 → 30,400at least +6,900 | 896 → 901at most +6 | +52.6 |
| /285527 Aug 2026, 14:37 UTC | 31 minutes | 30,400 → 39,000at least +8,500 | 901 → 908at most +8 | +64.7 |
| /285527 Aug 2026, 14:37 UTC | 31 minutes | 39,000 → 49,300at least +10,200 | 908 → 920at most +13 | +77.7 |
| /285527 Aug 2026, 14:37 UTC | 33 minutes | 49,300 → 59,600at least +10,200 | 920 → 923at most +4 | +77.7 |
| /285527 Aug 2026, 14:37 UTC | 35 minutes | 59,600 → 73,700at least +14,000 | 923 → 929at most +7 | +106.6 |
| /286529 Aug 2026, 16:09 UTC | 31 minutes | 16,900 → 27,300at least +10,300 | 834 → 841at most +8 | +78.5 |
| /286529 Aug 2026, 16:09 UTC | 35 minutes | 27,300 → 38,100at least +10,700 | 841 → 851at most +11 | +81.5 |
| /286529 Aug 2026, 16:09 UTC | 34 minutes | 38,100 → 49,600at least +11,400 | 851 → 860at most +10 | +86.8 |
| /286529 Aug 2026, 16:09 UTC | 30 minutes | 49,600 → 58,900at least +9,200 | 860 → 866at most +7 | +70.1 |
| /286529 Aug 2026, 16:09 UTC | 35 minutes | 58,900 → 77,200at least +18,200 | 866 → 873at most +8 | +138.6 |
| /28812 Sept 2026, 16:27 UTC | 32 minutes | 9,810 → 16,500at least +6,590 | 852 → 862at most +11 | +50.2 |
| /28812 Sept 2026, 16:27 UTC | 36 minutes | 16,500 → 26,400at least +9,800 | 862 → 871at most +10 | +74.6 |
| /28812 Sept 2026, 16:27 UTC | 34 minutes | 26,400 → 36,000at least +9,500 | 871 → 879at most +9 | +72.4 |
| /28812 Sept 2026, 16:27 UTC | 31 minutes | 36,000 → 45,500at least +9,400 | 879 → 889at most +11 | +71.6 |
| /28812 Sept 2026, 16:27 UTC | 31 minutes | 45,500 → 63,500at least +17,900 | 889 → 891at most +3 | +136.3 |
| /29015 Sept 2026, 16:55 UTC | 30 minutes | 22,700 → 34,900at least +12,100 | 844 → 850at most +7 | +92.2 |
| /29015 Sept 2026, 16:55 UTC | 35 minutes | 34,900 → 43,300at least +8,300 | 850 → 860at most +11 | +63.2 |
| /29015 Sept 2026, 16:55 UTC | 30 minutes | 43,300 → 50,500at least +7,100 | 860 → 870at most +11 | +54.1 |
| /29015 Sept 2026, 16:55 UTC | 34 minutes | 50,500 → 64,600at least +14,000 | 870 → 876at most +7 | +106.6 |
| /29015 Sept 2026, 16:55 UTC | 35 minutes | 64,600 → 81,200at least +16,500 | 876 → 882at most +7 | +125.7 |
| /30048 Sept 2026, 12:38 UTC | 36 minutes | 24,400 → 33,800at least +9,300 | 975 → 988at most +14 | +70.8 |
| /30048 Sept 2026, 12:38 UTC | 54 minutes | 36,400 → 49,400at least +12,900 | 1,001 → 1,013at most +22 | +98.3 |
| /30048 Sept 2026, 12:38 UTC | 55 minutes | 61,300 → 73,500at least +12,100 | 1,040 → 1,047at most +17 | +92.2 |
| /30048 Sept 2026, 12:38 UTC | 7.7 hours | 91,700 → 109,000at least +16,300 | 1,125 → 1,126at most +11 | +124.2 |
| /30048 Sept 2026, 12:38 UTC | 4 days | 109,000 → 135,000at least +25,000 | 1,126 → 1,131at most +15 | +190.4 |
Expected is the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say. It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the keys clone_copy · clone_source · view_reaction_decoupling, last confirmed 22 September 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’s posts match, word for word or near enough, posts on 4 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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 |
|---|---|---|
| 19 Sept 2026, 11:56 | 2,032,126 | -7,109 |
| 17 Sept 2026, 03:17 | 2,039,235 | +109 |
| 15 Sept 2026, 04:59 | 2,039,126 | +3,797 |
| 13 Sept 2026, 15:58 | 2,035,329 | +3,728 |
| 11 Sept 2026, 18:36 | 2,031,601 | -19,767 |
| 9 Sept 2026, 07:01 | 2,051,368 | -35,086 |
| 5 Sept 2026, 22:57 | 2,086,454 | +1,141 |
| 3 Sept 2026, 22:59 | 2,085,313 | +648 |
| 2 Sept 2026, 13:07 | 2,084,665 | +31,645 |
| 1 Sept 2026, 12:25 | 2,053,020 | +25,963 |
| 31 Aug 2026, 11:43 | 2,027,057 | -18,770 |
| 30 Aug 2026, 08:34 | 2,045,827 | +15,227 |
| 29 Aug 2026, 06:13 | 2,030,600 | -4,551 |
| 28 Aug 2026, 04:25 | 2,035,151 | -1,421 |
| 27 Aug 2026, 04:42 | 2,036,572 | +1,192 |
| 26 Aug 2026, 02:05 | 2,035,380 | +10,078 |
| 25 Aug 2026, 03:54 | 2,025,302 | +9,672 |
| 23 Aug 2026, 18:43 | 2,015,630 | +6,172 |
| 22 Aug 2026, 02:06 | 2,009,458 | -4,436 |
| 20 Aug 2026, 17:42 | 2,013,894 | first reading |
2,338 posts held, back to 11 September 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 3,490 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.
| Window | Rolling 30 days · latest post in window 22 September 2026 |
|---|---|
| Posts held | 2,338 (11 September 2025 – 22 September 2026) |
| Views total | 39,160,200 |
| Reactions total | 335,851 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 23 Sept 2026, 03:06 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 23 September 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 63 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.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 212 of this channel’s own posts over the last 30 days: across 202 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 7.4 hours of being posted; a typical post has already reached 13.1% of its 24-hour view count within the first hour, and 57.4% within the first six; the median 24-hour reach across those posts is 133,500 views — 6.57% of this channel’s own subscriber count (90th percentile 168,700).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /310619 Sept 2026, 16:10 UTC | 325 minutes – 1.6 hours old | 21,100 views ~854 reactions | 60 minutes: 13,700still climbing at last reading | not yet at 24h | 49 minutesprovisional — final view count still climbing |
| /310519 Sept 2026, 14:37 UTC | 617 minutes – 3.1 hours old | 39,900 views ~886 reactions | 60 minutes: 10,661 interp. → 3.0 hours: 39,900still climbing at last reading | not yet at 24h | 1.7 hoursprovisional — final view count still climbing |
| /310419 Sept 2026, 00:09 UTC | 3272 seconds – 18 hours old | 204,000 views ~1,870 reactions | 60 minutes: 106,180 interp. → 3.0 hours: 115,613 interp. → 6.0 hours: 156,000 → 12 hours: 193,000still climbing at last reading | not yet at 24h | 36 minutesprovisional — final view count still climbing |
| /310318 Sept 2026, 21:32 UTC | 373 minutes – 20 hours old | 155,000 views ~1,806 reactions | 60 minutes: 36,800 → 3.0 hours: 62,930 interp. → 6.0 hours: 86,600 → 12 hours: 144,000still climbing at last reading | not yet at 24h | 3.7 hoursprovisional — final view count still climbing |
| /310218 Sept 2026, 19:24 UTC | 4027 minutes – 22 hours old | 181,000 views ~1,010 reactions | 60 minutes: 30,900 → 3.0 hours: 55,700 → 6.0 hours: 110,000 → 12 hours: 171,000still climbing at last reading | not yet at 24h | 5.1 hoursprovisional — final view count still climbing |
| /310118 Sept 2026, 17:27 UTC | 4313 minutes – 24 hours old | 173,000 views ~1,482 reactions | 60 minutes: 17,581 interp. → 3.0 hours: 88,400 → 6.0 hours: 97,200 → 12 hours: 144,000 → 24 hours: 173,000still climbing at last reading | 173,000measured | 2.6 hoursprovisional — final view count still climbing |
| /310018 Sept 2026, 17:27 UTC | 4213 minutes – 24 hours old | 157,000 views ~1,188 reactions | 60 minutes: 13,785 interp. → 3.0 hours: 50,100 → 6.0 hours: 83,800 → 12 hours: 128,000 → 24 hours: 157,000still climbing at last reading | 157,000measured | 5.5 hoursprovisional — final view count still climbing |
| /309918 Sept 2026, 12:40 UTC | 51under a minute – 28 hours old | 157,000 views ~1,148 reactions | 60 minutes: 7,113 interp. → 3.0 hours: 15,237 interp. → 6.0 hours: 79,800 → 12 hours: 110,000 → 24 hours: 153,000still climbing at last reading | 153,000measured | 6.0 hours |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
547,705 reactions across 376 posts, in 6 distinct kinds. The most used accounts for 23.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 130,447 | 23.8% | |
| 🔥 | 119,930 | 21.9% | |
| 👍 | 118,735 | 21.7% | |
| 🎉 | 88,363 | 16.1% | |
| 💯 | 88,348 | 16.1% | |
| 👏 | 1,882 | 0.344% |
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 987 of the 1,000 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 1,767,300 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 19 May 2026 to 22 September 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @philgodlewskii4. 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 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 19 May 2026 to 22 September 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.
Trump, Belarus and ATOM ☝️ https://boostyfi.com/collective-purchase/3a75aa60-b7e4-44b3-b688-29fdd9f8604c?brand=satqm/?ref=philgodlewski
👍309🔥226❤201💯170🎉163
DONALD TRUMP. THE REPUBLIC OF BELARUS. A MASSIVE DEAL. AND ATOM IS ALREADY INSIDE THESE CHANGES. Not an outside journalist. Not an anonymous channel. Not an ATOM prediction. Donald Trump. President of the United States. Publicly, it's about the purchase of potash. But the power of this development is not limited to one commodity. The President of the United States has placed the Republic of Belarus at the center…
❤477🔥266👍226🎉195👏12
Photo, posted without a caption
❤407🔥281👍216🎉172💯170
Introducing TrueSigned 🏀 😄 TrueSigned is a new ATOM project, now in development. The market for signed collectibles has a serious forgery problem, and a buyer usually has no reliable way to check whether a specific item is genuine. TrueSigned solves this by giving each item a verifiable digital record, so its authenticity can be confirmed instead of taken on the seller's word. 🔓 Each registered item has a secure N…
🔥260❤222👍202🎉186💯156
😎
❤481🔥295👍255🎉240👏31
BREAKING - Trump says working on 'massive' fertilizer deal with Belarus bit.ly/4jg5OEI Follow @InsiderPaper for more news
❤607👍356🔥284🎉198💯154
Posted without readable text
❤237👍216🔥190🎉163💯163
Posted without readable text
👍243❤221💯170🎉167🔥153
😎
🔥729🎉316👍292❤259👏29
Video, posted without a caption
🔥1,160🎉448❤373👍304👏69
Next LIVE ☝️ Plus a few updates 😎
👍681❤387💯197🔥184🎉168
🔔 ATQM is consolidating on BoostyFi The Collective Purchases in AgTech, MedTech and Mobile have closed. Thank you to everyone who took part — the funds went where you chose. 🔹 These directions continue as ATOM businesses: ➖ AgTech — ATOM Green Capital ➖ MedTech — ATOM Health Capital ➖ Mobile — ATOM Mobile What changes is how you buy in, not what gets built. 🔹 What's different from now on There's just ATQM. New …
❤260👍230🔥168💯166🎉164
Showing the 12 most recent of 2,338 posts we hold for @philgodlewskii4. 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.
@philgodlewskii4 edited 7 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.
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.
Which track do you like the most? 🎵
The shares total 128%, 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 1,000 most recent posts we hold (the sample is capped at 1,000), published 19 May 2026 to 22 September 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.
Republishes 54 registered channels. The 48 listed are the ones this channel has forwarded most; the rest are counted here but not each listed.
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 5 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.
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.
@philgodlewskii4 named 3 handles 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.
References a handle that is not a live channel — we have no record it ever was one.
91 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Phil Godlewski 4.0” (@philgodlewskii4), 2,032,126 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/philgodlewskii4.
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.