Photo, posted without a caption
🔥966❤389👍292🎉230👏45

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 · Posts recorded as deleted · Polls · Citations · Handles named that no longer answer · Domains linked from posts · Cite this entry
2,006,246subscribers
-37,404 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 | 7 November 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 7 November 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 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 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 259 of the 358 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.0100 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /334516 Oct 2026, 16:35 UTC | 30 minutes | 19,500 → 27,000at least +7,400 | 883 → 898at most +16 | +73.8 |
| /334516 Oct 2026, 16:35 UTC | 35 minutes | 27,000 → 33,400at least +6,300 | 898 → 910at most +13 | +62.8 |
| /334516 Oct 2026, 16:35 UTC | 35 minutes | 33,400 → 40,600at least +7,100 | 910 → 921at most +12 | +70.8 |
| /334516 Oct 2026, 16:35 UTC | 35 minutes | 40,600 → 47,800at least +7,100 | 921 → 928at most +8 | +70.8 |
| /334516 Oct 2026, 16:35 UTC | 51 minutes | 60,100 → 71,400at least +11,200 | 940 → 950at most +11 | +111.6 |
| /334516 Oct 2026, 16:35 UTC | 4 days | 122,000 → 201,000at least +78,000 | 1,028 → 1,036at most +18 | +777.5 |
| /334816 Oct 2026, 17:34 UTC | 35 minutes | 25,500 → 34,800at least +9,200 | 884 → 892at most +9 | +91.7 |
| /334816 Oct 2026, 17:34 UTC | 30 minutes | 34,800 → 41,000at least +6,100 | 892 → 901at most +10 | +60.8 |
| /334816 Oct 2026, 17:34 UTC | 35 minutes | 41,000 → 48,200at least +7,100 | 901 → 910at most +10 | +70.8 |
| /334816 Oct 2026, 17:34 UTC | 51 minutes | 48,200 → 57,600at least +9,300 | 910 → 922at most +13 | +92.7 |
| /334816 Oct 2026, 17:34 UTC | 54 minutes | 64,700 → 79,700at least +14,900 | 930 → 937at most +8 | +148.5 |
| /334816 Oct 2026, 17:34 UTC | 4 days | 121,000 → 199,000at least +77,000 | 1,007 → 1,014at most +17 | +767.5 |
| /334916 Oct 2026, 17:37 UTC | 35 minutes | 25,500 → 34,700at least +9,100 | 882 → 894at most +13 | +90.7 |
| /334916 Oct 2026, 17:37 UTC | 30 minutes | 34,700 → 41,000at least +6,200 | 894 → 902at most +9 | +61.8 |
| /334916 Oct 2026, 17:37 UTC | 35 minutes | 41,000 → 48,200at least +7,100 | 902 → 913at most +12 | +70.8 |
| /334916 Oct 2026, 17:37 UTC | 51 minutes | 48,200 → 56,900at least +8,600 | 913 → 930at most +18 | +85.7 |
| /334916 Oct 2026, 17:37 UTC | 54 minutes | 64,100 → 79,500at least +15,300 | 939 → 946at most +8 | +152.5 |
| /334916 Oct 2026, 17:37 UTC | 4 days | 115,000 → 211,000at least +95,000 | 1,026 → 1,031at most +15 | +947.0 |
| /328514 Oct 2026, 05:18 UTC | 35 minutes | 19,300 → 28,900at least +9,500 | 887 → 908at most +22 | +94.7 |
| /328514 Oct 2026, 05:18 UTC | 35 minutes | 28,900 → 40,800at least +11,800 | 908 → 923at most +16 | +117.6 |
| /328514 Oct 2026, 05:18 UTC | 30 minutes | 40,800 → 51,000at least +10,100 | 923 → 934at most +12 | +100.7 |
| /328514 Oct 2026, 05:18 UTC | 35 minutes | 51,000 → 59,400at least +8,300 | 934 → 946at most +13 | +82.7 |
| /328514 Oct 2026, 05:18 UTC | 4 days | 197,000 → 239,000at least +41,000 | 1,594 → 1,625at most +41 | +408.7 |
| /333116 Oct 2026, 15:36 UTC | 30 minutes | 50,400 → 65,700at least +15,200 | 948 → 965at most +18 | +151.5 |
| /333116 Oct 2026, 15:36 UTC | 30 minutes | 65,700 → 91,900at least +26,100 | 965 → 980at most +16 | +260.2 |
| /333116 Oct 2026, 15:36 UTC | 35 minutes | 91,900 → 123,000at least +30,100 | 980 → 993at most +14 | +300.0 |
| /333116 Oct 2026, 15:36 UTC | 3.1 hours | 123,000 → 184,000at least +60,000 | 993 → 1,062at most +79 | +598.1 |
| /333116 Oct 2026, 15:36 UTC | 5 days | 218,000 → 279,000at least +60,000 | 1,186 → 1,209at most +33 | +598.1 |
| /333316 Oct 2026, 15:37 UTC | 30 minutes | 48,100 → 64,300at least +16,100 | 930 → 945at most +16 | +160.5 |
| /333316 Oct 2026, 15:37 UTC | 30 minutes | 64,300 → 90,500at least +26,100 | 945 → 961at most +17 | +260.2 |
| /333316 Oct 2026, 15:37 UTC | 35 minutes | 90,500 → 120,000at least +28,500 | 961 → 974at most +14 | +284.1 |
| /333316 Oct 2026, 15:37 UTC | 35 minutes | 120,000 → 165,000at least +44,000 | 974 → 985at most +12 | +438.6 |
| /333316 Oct 2026, 15:37 UTC | 5 days | 218,000 → 277,000at least +58,000 | 1,156 → 1,176at most +30 | +578.1 |
| /334116 Oct 2026, 16:01 UTC | 30 minutes | 28,700 → 42,900at least +14,100 | 858 → 868at most +11 | +140.5 |
| /334116 Oct 2026, 16:01 UTC | 30 minutes | 42,900 → 66,000at least +23,000 | 868 → 877at most +10 | +229.3 |
| /334116 Oct 2026, 16:01 UTC | 35 minutes | 66,000 → 91,100at least +25,000 | 877 → 886at most +10 | +249.2 |
| /334116 Oct 2026, 16:01 UTC | 35 minutes | 91,100 → 133,000at least +40,900 | 886 → 893at most +8 | +407.7 |
| /334116 Oct 2026, 16:01 UTC | 4 days | 175,000 → 229,000at least +53,000 | 984 → 989at most +6 | +528.3 |
| /334316 Oct 2026, 16:34 UTC | 30 minutes | 27,000 → 41,400at least +14,300 | 870 → 885at most +16 | +142.5 |
| /334316 Oct 2026, 16:34 UTC | 35 minutes | 41,400 → 52,700at least +11,200 | 885 → 898at most +14 | +111.6 |
| /334316 Oct 2026, 16:34 UTC | 35 minutes | 52,700 → 71,900at least +19,100 | 898 → 907at most +10 | +190.4 |
| /334316 Oct 2026, 16:34 UTC | 35 minutes | 71,900 → 99,000at least +27,000 | 907 → 915at most +9 | +269.1 |
| /334316 Oct 2026, 16:34 UTC | 30 minutes | 99,000 → 131,000at least +31,000 | 915 → 925at most +11 | +309.0 |
| /334416 Oct 2026, 16:35 UTC | 35 minutes | 25,400 → 32,600at least +7,100 | 917 → 930at most +14 | +70.8 |
| /334416 Oct 2026, 16:35 UTC | 35 minutes | 32,600 → 39,800at least +7,100 | 930 → 944at most +15 | +70.8 |
| /334416 Oct 2026, 16:35 UTC | 35 minutes | 39,800 → 47,000at least +7,100 | 944 → 958at most +15 | +70.8 |
| /334416 Oct 2026, 16:35 UTC | 51 minutes | 58,200 → 68,600at least +10,300 | 978 → 991at most +14 | +102.7 |
| /334416 Oct 2026, 16:35 UTC | 4 days | 121,000 → 194,000at least +72,000 | 1,092 → 1,104at most +22 | +717.7 |
| /334616 Oct 2026, 16:47 UTC | 35 minutes | 24,400 → 32,800at least +8,300 | 879 → 890at most +12 | +82.7 |
| /334616 Oct 2026, 16:47 UTC | 35 minutes | 32,800 → 40,100at least +7,200 | 890 → 901at most +12 | +71.8 |
| /334616 Oct 2026, 16:47 UTC | 35 minutes | 40,100 → 46,300at least +6,100 | 901 → 909at most +9 | +60.8 |
| /334616 Oct 2026, 16:47 UTC | 51 minutes | 57,600 → 67,500at least +9,800 | 925 → 937at most +13 | +97.7 |
| /334616 Oct 2026, 16:47 UTC | 4 days | 118,000 → 194,000at least +75,000 | 1,014 → 1,023at most +19 | +747.6 |
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 7 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’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 |
|---|---|---|
| 7 Nov 2026, 06:34 | 2,006,246 | -2,723 |
| 6 Nov 2026, 07:10 | 2,008,969 | -4,455 |
| 5 Nov 2026, 09:15 | 2,013,424 | +5,298 |
| 4 Nov 2026, 11:50 | 2,008,126 | -7,675 |
| 3 Nov 2026, 13:26 | 2,015,801 | +2,395 |
| 2 Nov 2026, 10:26 | 2,013,406 | +1,026 |
| 1 Nov 2026, 07:39 | 2,012,380 | +5,357 |
| 31 Oct 2026, 11:07 | 2,007,023 | -18,538 |
| 30 Oct 2026, 09:56 | 2,025,561 | -5,303 |
| 29 Oct 2026, 11:59 | 2,030,864 | -3,794 |
| 28 Oct 2026, 08:56 | 2,034,658 | +2,021 |
| 27 Oct 2026, 11:08 | 2,032,637 | +1,574 |
| 26 Oct 2026, 13:16 | 2,031,063 | +1,523 |
| 25 Oct 2026, 11:55 | 2,029,540 | +5,365 |
| 24 Oct 2026, 12:16 | 2,024,175 | +6,857 |
| 23 Oct 2026, 11:28 | 2,017,318 | -855 |
| 22 Oct 2026, 09:54 | 2,018,173 | -10,286 |
| 21 Oct 2026, 03:17 | 2,028,459 | -8,320 |
| 19 Oct 2026, 23:16 | 2,036,779 | -7,899 |
| 19 Oct 2026, 00:49 | 2,044,678 | first reading |
2,837 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,586 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 7 November 2026 |
|---|---|
| Posts held | 2,837 (11 September 2025 – 7 November 2026) |
| Views total | 60,654,080 |
| Reactions total | 646,892 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Nov 2026, 20:30 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 7 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 183 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 359 of this channel’s own posts over the last 30 days: across 336 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 20 hours of being posted; a typical post has already reached 23.0% of its 24-hour view count within the first hour, and 67.0% within the first six; the median 24-hour reach across those posts is 93,500 views — 4.66% of this channel’s own subscriber count (90th percentile 164,300).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /37947 Nov 2026, 17:56 UTC | 519 minutes – 2.6 hours old | 59,900 views ~1,922 reactions | 60 minutes: 53,251 interp.still climbing at last reading | not yet at 24h | 19 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /37937 Nov 2026, 14:30 UTC | 1211 minutes – 6.0 hours old | 73,600 views ~1,778 reactions | 60 minutes: 36,858 interp. → 3.0 hours: 48,383 interp. → 6.0 hours: 73,600still climbing at last reading | not yet at 24h | 60 minutesprovisional — final view count still climbing |
| /37927 Nov 2026, 13:40 UTC | 1330 minutes – 6.8 hours old | 37,700 views ~1,823 reactions | 60 minutes: 8,990 → 3.0 hours: 18,500 → 6.0 hours: 29,800still climbing at last reading | not yet at 24h | 3.1 hoursprovisional — final view count still climbing |
| /37917 Nov 2026, 13:09 UTC | 1427 minutes – 7.4 hours old | 60,800 views ~1,125 reactions | 60 minutes: 37,300 → 3.0 hours: 49,200 → 6.0 hours: 59,500still climbing at last reading | not yet at 24h | 27 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /37907 Nov 2026, 12:52 UTC | 158 minutes – 7.6 hours old | 60,800 views ~2,005 reactions | 60 minutes: 39,062 interp. → 3.0 hours: 51,027 interp. → 6.0 hours: 57,800still climbing at last reading | not yet at 24h | 11 minutesprovisional — final view count still climbing |
| /37897 Nov 2026, 12:44 UTC | 1517 minutes – 7.8 hours old | 30,900 views ~2,256 reactions | 60 minutes: 7,897 interp. → 3.0 hours: 18,354 interp. → 6.0 hours: 27,800still climbing at last reading | not yet at 24h | 2.2 hoursprovisional — final view count still climbing |
| /37887 Nov 2026, 12:43 UTC | 1517 minutes – 7.8 hours old | 30,200 views ~2,004 reactions | 60 minutes: 7,333 interp. → 3.0 hours: 18,465 interp. → 6.0 hours: 28,000still climbing at last reading | not yet at 24h | 2.2 hoursprovisional — final view count still climbing |
| /37857 Nov 2026, 02:04 UTC | 355 minutes – 18 hours old | 28,800 views ~1,669 reactions | 60 minutes: 8,120 → 3.0 hours: 13,777 interp. → 6.0 hours: 17,900 → 12 hours: 24,900still climbing at last reading | not yet at 24h | 3.3 hoursprovisional — final view count still climbing |
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.
1,356,036 reactions across 865 posts, in 6 distinct kinds. The most used accounts for 24.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 328,727 | 24.2% | |
| 🔥 | 318,161 | 23.5% | |
| 👍 | 287,656 | 21.2% | |
| 💯 | 222,860 | 16.4% | |
| 🎉 | 188,417 | 13.9% | |
| 👏 | 10,215 | 0.753% |
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 980 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,671,487 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 14 July 2026 to 7 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.
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 14 July 2026 to 7 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.
Telegram’s own ‘edited’ marker: 8 of 388 posts held from the last 30 days (2.06%) 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).
Photo, posted without a caption
🔥966❤389👍292🎉230👏45
Photo, posted without a caption
🔥904👍381❤245🎉212👏36
Phil did tell us awhile back that some of president Trumps cabinet would not be there for the duration. Hence, the replacement of Susie Wiles.
👍842💯411❤225🔥181🎉164
hey pham I know I havent mentioned much about ATOM lately, mainly because of the happenings with the midterms, etc. But this ATQM expo pack is almost at it's maximum and will expire on November 30th. Remember — ATQM is no longer available for sale once this pack expires. Boostyfi.com/?ref=philgodlewski
👍441🎉264❤218💯196👏6
Vance is literally telling is that it's about to happen.
🔥1,000❤323🎉270💯208👍204
🚨 JUST IN: Incoming WH Chief of Staff Stephen Miller just EMERGED with president Trump at Mar-a-Lago and said it PERFECTLY "This man took a BULLET for us. He faced down life in PRISON for us...We need to stand with the man who has stood with us and this country with every fiber of his being! It is the honor of my life to be President Trump's chief of staff. And I swear to you, and I pledge to you, Mr. President, my …
❤1,170🔥485💯321👍221👏59
Demons are trembling at the announcement of Steven Miller’s new role as Chief of Staff of the White House. Liberals are saying Trump is about to run these next two years from beneath the Ballroom, and they are saying he’s going to run the show WITHOUT Congress. Steven Miller has just been given control of the White House. Pete Hegseth posted today that “Patriots are in control” Gods Army has been activated. We’ve…
🔥1,000❤462💯261🎉248👏33
https://x.com/WallStreetApes/status/2118857294494720367/photo/2?a=b2qAmvY_cX2Mj89s8f0&s=19
👍614💯402🔥275❤196🎉182
Phil speaks has a live stream and within less than 24 hours the secretary of war. Quotes a Q drop. Then Phil has a live stream yesterday and President Trump says you’re gonna see a lot going on in the next week or two. What like 10 days? Could it be that Phil’s the captain of the ship? Because I think he is, it is very interesting. The Delta live stream Phil delta for today is 10 days.darkness. Quite interesting.…
❤612🔥260👍120💯39👏20
https://x.com/WallStreetApes/status/2118829073153839421?a=j8Atri-8ymfiUP4eo7M&s=19
❤509💯383🔥292👍198🎉157
Fraud 💯
💯1,370🔥267👍216❤190🎉181
Sticker, posted without a caption
❤546🔥395💯276🎉213👏20
Showing the 12 most recent of 2,837 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 10 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 23 posts on @philgodlewskii4 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 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
There's a LOT happening at ATOM right now — and with the Expo coming, there's about to be a whole lot more to show you. So before it ramps up, I want to get the mix right for you. Straight answer — how's it feeling? 👇
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
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 14 July 2026 to 7 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.
Republishes 64 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 5 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“Phil Godlewski 4.0” (@philgodlewskii4), 2,006,246 subscribers as measured 7 November 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.