2 spots and we are full for the month ✌️
🤬3👎2👻2

Channel
@JPYslayerTeam
On this record: Topic · Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry
49subscribers
-20 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002690150736 |
|---|---|
| Type | Channel |
| Username | @JPYslayerTeam |
| Created | Between 1 March 2025 and 29 May 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 8 October 2026 |
| On Telegram | t.me/JPYslayerTeam |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 29 September 2026 and assigned it the closest of 31 fixed categories, at 48% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Oct 2026, 20:36 | 49 | -1 |
| 28 Sept 2026, 17:40 | 50 | -5 |
| 14 Sept 2026, 15:56 | 55 | -4 |
| 6 Sept 2026, 14:16 | 59 | -2 |
| 28 Aug 2026, 19:34 | 61 | -3 |
| 21 Aug 2026, 18:08 | 64 | -1 |
| 14 Aug 2026, 21:35 | 65 | -4 |
| 10 Aug 2026, 00:17 | 69 | no change |
| 7 Aug 2026, 17:38 | 69 | first reading |
20 posts held, back to 29 May 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 page of 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 1 June 2025. An engagement rate over an empty window would be a number about nothing.
39 reactions across 9 posts, in 6 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👻 | 13 | 33.3% | |
| 🤬 | 12 | 30.8% | |
| 👎 | 11 | 28.2% | |
| ❤ | 1 | 2.56% | |
| 🤪 | 1 | 2.56% | |
| 🤮 | 1 | 2.56% |
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 9 of the 20 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 39 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 29 May 2025 to 1 June 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
2 spots and we are full for the month ✌️
🤬3👎2👻2
6 spots are taken 4 spots remaining and we close vip acess for a month ✔️
👎2👻2🤬2
3 Spots are taken. 7 Spots remaining and we close vip acess till July. ✔️
🤬3👻2👎1
🚨 VIP JPY TRADING CHANNEL LAUNCHING JUNE 🚨 We’ve spent the last 2 weeks showing what we can do – and now we’re ready to go private. We only trade JPY pairs – that’s where we’ve found our edge. We are a team of 3 experienced traders with decades of combined experience. These are not random results – we deliver day after day, week after week, month after month. Now we’re ready to share our trades and strategy – but onl…
👻2❤1👎1🤬1
♻️ Monthly Report ♻️ 🟢 GBPJPY Sell 91.4 Pips 9.59% 🟢 GBPJPY Sell 43.8 Pips 5.16% 🟢 EURJPY Sell 35.6 Pips 3.98% 🔴 GBPJPY Sell -9.7 Pips -1.14% 🟢 USDJPY Sell 80.1 Pips 9.57% 🔴 GBPJPY Sell -13.8 Pips -1.12% 🟢 GBPJPY Buy 40.0 Pips 5.26% 🟢 USDJPY Sell 39.2 Pips 5.01% 🟢 GBPJPY Sell 20.3 Pips 2.47% 🟢 GBPJPY Sell 26.2 Pips 3.41% 🟢 USDJPY Sell 28.0 Pips 3.52% 🟢 USDJPY Sell 23.3 Pips 3.08% 🔴 EURJPY Sell -…
👎1👻1🤬1
♻️ Weekly Report ♻️ 🔴 GBPJPY Sell -13.8 Pips -1.12% 🟢 GBPJPY Buy 40.0 Pips 5.26% 🟢 USDJPY Sell 39.2 Pips 5.01% 🟢 GBPJPY Sell 20.3 Pips 2.47% 🟢 GBPJPY Sell 26.2 Pips 3.41% 🟢 USDJPY Sell 28.0 Pips 3.52% 🟢 USDJPY Sell 23.3 Pips 3.08% 🔴 EURJPY Sell -11.7 Pips -1.57% 🟢 USDJPY Buy 28.8 Pips 3.85% Partial Orders are merged Pips: 180.3 Profit: 23.91% Wins: 7 Losses: 2 BE: 0 Winrate: 78%
👎1👻1🤬1
♻️ Daily Report ♻️ 🟢 GBPJPY Sell 26.2 Pips 3.41% 🟢 USDJPY Sell 28.0 Pips 3.52% 🟢 USDJPY Sell 23.3 Pips 3.08% 🔴 EURJPY Sell -11.7 Pips -1.57% 🟢 USDJPY Buy 28.8 Pips 3.85% Partial Orders are merged Pips: 106.3 Profit: 9.21% Wins: 4 Losses: 1 BE: 0 Winrate: 80%
🟢 CLOSED - USDJPY Buy 🟢 # 285207078 --------{ CLOSED }--------- Entry: 143.578 Exit: 143.866 Profit: 3.85% Pips: 28.8 --------------------------- ⏱️ Duration: 0h 31m 36s 👉 Closed Manually
🔴 CLOSED - EURJPY Sell 🔴 # 285192576 --------{ CLOSED }--------- Entry: 162.986 Exit: 163.103 Profit: -1.57% Pips: -11.7 --------------------------- ⏱️ Duration: 0h 38m 48s ⭕ Closed due to Stoploss
NEW ORDER - USDJPY Buy 📈 # 285207078 ----------{ NEW }---------- Entry: 143.578 SL: 143.400 [17.8 Pips] TP: 144.000 [42.2 Pips] RR: 2.37 ---------------------------
NEW ORDER - EURJPY Sell 📉 # 285192576 ----------{ NEW }---------- Entry: 162.986 SL: 163.100 [11.4 Pips] TP: 162.300 [68.6 Pips] RR: 6.02 ---------------------------
🟢 CLOSED - USDJPY Sell 🟢 # 285095886 --------{ CLOSED }--------- Entry: 143.955 Exit: 143.722 Profit: 3.08% Pips: 23.3 --------------------------- ⏱️ Duration: 0h 50m 29s 👉 Closed Manually
Showing the 12 most recent of 20 posts we hold for @JPYslayerTeam. 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.
@JPYslayerTeam 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.
References a handle that is not a live channel — we have no record it ever was one.
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 8 October 2026 — this entry's latest reading, not the date you are reading this.
“JPYslayerTeam” (@JPYslayerTeam), 49 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/JPYslayerTeam.
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.