New FedBan Fed: ๐ฆแดนแดฌหขแตแดฑแดฟ แดผแถ แถ แดตแดณแดดแตแดฑแดฟ๐ฆ( @phoenix_f3d_v38 ) FedAdmin: ๐โ๐โ๐ ใก ๐๐๐๐ User: LEVI User ID: 6614533912 Reason: we cant tolerate disrespecting of any women/admin of the GC . Don't unban this person https://graph.org/file/f3930645dcf9e3afec8d2.jpg

Channel
๐ฆ๐๐ผ๐๐๐๐ ๐๐ ๐๐๐๐๐๐๐๐ฆ {แดสแดแดษดษชx าแดแด แด 38}
@phoenixfedlogs_v38
On this record: Growth ยท Engagement ยท What this channel posts ยท Posts ยท Citations ยท Handles named that no longer answer ยท Cite this entry
2subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register ยท movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001413761639 |
|---|---|
| Type | Channel |
| Username | @phoenixfedlogs_v38 |
| Description | Welcome To PHOENIX FED V38 Our Tag - โโฌ-๐พ๐๐พ-โฌโ About Phoenix Feds - @Phoenix_empire Founder - @Phoenixwarmed Fed owner - @crazypagal01 Fed Log's Channel - @Phoenixfedlogs_V38 Our Hub - @CFChub |
| Created | Between 1 April 2019 and 30 September 2021โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/phoenixfedlogs_v38 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 07:32 | 2 | no change |
| 12 Aug 2026, 10:34 | 2 | first reading |
Engagement
20 posts held, back to 24 March 2024 โ 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute โ we hold 20 posts for this entry, the most recent from 28 August 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 1
- Links
- 364
Lifetime counters from Telegramโs own channel header, read 14 August 2026 โ not the date at the top of this page, which is when the subscriber count was last read. Below Telegramโs rounding threshold, so these counts are exact.
Recent posts
New FedBan Fed: ๐ฆแดนแดฌหขแตแดฑแดฟ แดผแถ แถ แดตแดณแดดแตแดฑแดฟ๐ฆ( @phoenix_f3d_v38 ) FedAdmin: ๐โ๐โ๐ ใก ๐๐๐๐ User: kkkin User ID: 6222631479 Reason: sending 18+ content to girls and abusing in dm
New FedBan Fed: ๐ฆแดนแดฌหขแตแดฑแดฟ แดผแถ แถ แดตแดณแดดแตแดฑแดฟ๐ฆ( @phoenix_f3d_v38 ) FedAdmin: ๐โ๐โ๐ ใก ๐๐๐๐ User: ๐๐ง๐ฎ๐ฆ User ID: 7302566085 Reason: ABUSING IN THE GRP TO ADMINS
New FedBan Fed: ๐ฆแดนแดฌหขแตแดฑแดฟ แดผแถ แถ แดตแดณแดดแตแดฑแดฟ๐ฆ( @phoenix_f3d_v38 ) FedAdmin: ๐โ๐โ๐ ใก ๐๐๐๐ User: Jayesh Pawar User ID: 7076173680 Reason: #ULTMassBanned
New FedBan Fed: ๐ฆแดนแดฌหขแตแดฑแดฟ แดผแถ แถ แดตแดณแดดแตแดฑแดฟ๐ฆ( @phoenix_f3d_v38 ) FedAdmin: ๐โ๐โ๐ ใก ๐๐๐๐ User: - โ ๐ค ๐ ษฃ แฆ ๊ซ ษด ๐ฒ หน ๐ ๐ หผ๏น๐ฎ๐ณ๏นโ ๐ธ User ID: 6838326214 Reason: ABUSING GIRLS IN THE GRP
New FedBan Fed: ๐ฆแดนแดฌหขแตแดฑแดฟ แดผแถ แถ แดตแดณแดดแตแดฑแดฟ๐ฆ( @phoenix_f3d_v38 ) FedAdmin: ๐โ๐โ๐ ใก ๐๐๐๐ User: โคออ ๐ แด แด ส ษช ษด ๊ญ หฃ โข แฏค User ID: 7368342025 Reason: ABUSING GIRLS IN THE GRP
New FedBan Fed: ๐ฆแดนแดฌหขแตแดฑแดฟ แดผแถ แถ แดตแดณแดดแตแดฑแดฟ๐ฆ( @phoenix_f3d_v38 ) FedAdmin: ๐โ๐โ๐ ใก ๐๐๐๐ User: !๐๐ฆ๐กโ! User ID: 6568622150 Reason: Scamming peoples by selling groups . DONOT UNBAN .
New FedBan Fed: ๐ฆแดนแดฌหขแตแดฑแดฟ แดผแถ แถ แดตแดณแดดแตแดฑแดฟ๐ฆ( @phoenix_f3d_v38 ) FedAdmin: ๐โ๐โ๐ ใก ๐๐๐๐ User: ๐ฐ๐โธผโโ๐ ๐ฎ ๐ต ๐ชโ๐พ๐ญุขโโ๐ค๐ ๊ฏญ User ID: 2030238685 Reason: Scamming peoples by selling groups . DONOT UNBAN . for proof https://graph.org/file/6a882d1e1c3196a4c0131.jpg
New FedBan Fed: ๐ฆแดนแดฌหขแตแดฑแดฟ แดผแถ แถ แดตแดณแดดแตแดฑแดฟ๐ฆ( @phoenix_f3d_v38 ) FedAdmin: ๐โ๐โ๐ ใก ๐๐๐๐ User: ๐ฮฑึแัฮฑ๊ญฬฝอ๐๊ฏญโผโโอก User ID: 7214926834 Reason: Scamming peoples by asking selling group for proof https://graph.org/file/c25e372c03ceffea27add.jpg
New FedBan Fed: ๐ฆแดนแดฌหขแตแดฑแดฟ แดผแถ แถ แดตแดณแดดแตแดฑแดฟ๐ฆ( @phoenix_f3d_v38 ) FedAdmin: ๐โ๐โ๐ ใก ๐๐๐๐ User: Rรณzsika Rothschild ๐ User ID: 7217355089 Reason: DOING DM AND ASKING MONEY ๐ค
#GOODBYE: Chat: 3 User: EPIC User ID: 6215255401 Message link: link
#GROUPTRANSFER: Chat: 3 Admin: EPIC User: ๐จ๐๐๐๐ User ID: 363162905 Message link: No message link for manual actions
Showing the 12 most recent of 20 posts we hold for @phoenixfedlogs_v38. 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 โ 1,372,866 of 1,480,688entries 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.
Mentions
Named by 1 registered channel โ 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.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channelโs posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@phoenixfedlogs_v38 named 1 handle 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.
Never seen alive
References a handle that is not a live channel โ we have no record it ever was one.
named in 6 posts, 15 August 2026 โ 15 August 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 14 August 2026 โ this entry's latest reading, not the date you are reading this.
โ๐ฆ๐๐ผ๐๐๐๐ ๐๐ ๐๐๐๐๐๐๐๐ฆ {แดสแดแดษดษชx าแดแด แด 38}โ (@phoenixfedlogs_v38), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/phoenixfedlogs_v38.
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.