😚 사기를 당하는 이유는? "블랙리스트" 제휴만 쓰면되는데 뭐 홍보글보고 쓰다 당하는겁니다... 이걸로 "종결" 해드리겠습니다! 사이트 아무곳이나 쓰면"핑돈환전"장묶임😱 이방저방드가있는 업자들 사기꾼도 많아요😱 💗 [블랙리스트제휴를써야하는이유] 😚 블랙리스트 문의 : [바로가기] 💗💗💗💗💗💗💗 : [바로가기] 💗💗💗💗💗💗💗 : [바로가기]

Channel
블랙리스트(SNS사기피해공유)
@vsvs1119
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
55,377subscribers
-3,108 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1002021417803 |
|---|---|
| Type | Channel |
| Username | @vsvs1119 |
| Description | ⚫️블랙리스트⚫️ - 사기피해 공유 @qweqwe1940 "사람이 죄를 지었으면, 벌을 받는 게 세상 이치" We created this channel to prevent damage by sharing information with people. There are no spam ads on our channel. |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/vsvs1119 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 15:46 | 55,377 | -817 |
| 12 Aug 2026, 17:38 | 56,194 | -298 |
| 11 Aug 2026, 20:22 | 56,492 | -681 |
| 10 Aug 2026, 22:36 | 57,173 | -272 |
| 9 Aug 2026, 20:11 | 57,445 | -31 |
| 8 Aug 2026, 18:44 | 57,476 | -1,009 |
| 7 Aug 2026, 19:30 | 58,485 | no change |
| 7 Aug 2026, 19:19 | 58,485 | first reading |
Engagement
36 posts held, back to 6 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.10%
- avg views ÷ 55,377 subscribers
- Avg views / post
- 1,170
- 36 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 36
- of 36 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.
| Window | Rolling 30 days · latest post in window 13 August 2026 |
|---|---|
| Posts held | 36 (6 August 2026 – 13 August 2026) |
| Views total | 41,954 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Aug 2026, 00:14 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.
What this channel posts
- Photos
- ≈8,510
- Videos
- ≈161
- Links
- ≈1,570
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. 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.
- Video runtime
- 3s
- Average length
- 1s
Measured directly from 3 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.
Recent posts
❤️ VIP 본방 관련 공지사항 💗업자기준 = 휴대폰 영상녹화 본인 텔레아이디 나와야함 , 업무 내역 녹화 해서 보내 주시면됩니다. (보안 , 노출 걱정 안해도됩니다) 😚블랙리스트 본방 규정 확인필수 VIP 소통과 사기꾼 확인 홍보 절대불가 😚블랙리스트 @QWEQWE1940
❤️ 확인 "필수" 입니다 💗 [블랙리스트 운영 목적] 💗 [제보 양식 바로가기] 💗 [제휴 가이드 바로가기] 💗 [그룹방 총 정리 안내글] 💗 [사기꾼 검색 방법 최신화] 💗 [중개글 안내글 바로가기] 💗 [사칭주의 안내글 바로가기]
대포통장 107개로 불법도박 수익 5062억 세탁…19명 검거 불법 도박사이트 운영자들과 공모해 대포통장 107개로 5000억원대 범죄수익을 세탁한 전문 자금세탁 조직이 검찰에 넘겨졌다. 광주경찰청 광역범죄수사대는 대구와 부산에 거점을 둔 자금세탁 조직 총책·관리책 등 19명을 범죄수익 은닉 규제법 위반, 범죄단체조직·가입·활동 등 혐의로 검거해 송치(12명 구속·7명 불구속)했다고 10일 밝혔다. 또 이들에게 대가를 받고 대포통장과 체크카드 등 접근매체를 넘긴 명의 제공자 160명은 전자금융거래법 위반 등 혐의로 검거했다. 이들은 불법 도박사이트 운영자들로부터 세탁을 의뢰받아 대포통장으로 범죄수익을 입금받은 뒤 여러 계좌로 반복 이체하거나 현금으로 인출하는 방식으로 자금을 세탁한 혐의를 받는다. 조사 결과 대구를 거점으로 한 A조직은…
😚 사기꾼 박제 등록알림 ➿➿➿➿➿➿➿➿➿ 💗닉네임 : 달 인 💗텔레그렘 ID : @DALN010 💗고유번호 : 8699722194 ➿➿➿➿➿➿➿➿➿ 😚해당 제보 내용 8월10일에 단순 은행 전화해서 녹음만해주고 보내주면 4500원 지급해주겠다 하여 진행하였지만 폰이 꺼져있었다 오늘주겠다 영어치다가 이제는 아예 연락을 안보내요 ++ 이새끼 전계정 @jo_ker112 , @JSMLB77 ❤️블랙리스트 답변 수 차례 박제된 인물이며 주의 하시길 바랍니다 😚 블랙리스트 문의 : [바로가기] 💗💗💗💗💗💗💗 : [바로가기] 💗💗💗💗💗💗💗 : [바로가기]
😚사칭새끼들 역겹네 수년간 억대는 해처먹었겠구나 지긋지긋 하다 증말 이글 보고계신 모든분들 연락처추가 , 텔대화남겨도됨 블랙리스트 최대표 @QWEQWE1940 사칭 주의 🙏🏻
😚 사기꾼 박제 등록알림 ➿➿➿➿➿➿➿➿➿ 💗닉네임 : HAYEON [ 하연 ] 💗텔레그렘 ID : @HAYEON_010 💗고유번호 : 8450606671 ➿➿➿➿➿➿➿➿➿ 😚해당 제보 내용 토스 커뮤니티 팔려고 했고 즉정이라고 했는데 사용하고 준다고 하길래 등초본 다줄테니 먹튀 안한다고 하니까 받고도 30분 걸린다고 하고 영어 하길래 즉정 아니냐니까 욕하고 대화방 밀었습니다 ❤️블랙리스트 답변 애당초 "즉정" 이라고 본인채널에 본인이 그럴싸하게 홍보하는데 막상 진행하면 딜레이태우니 결국 박제되는 엔딩 😚 블랙리스트 문의 : [바로가기] 💗💗💗💗💗💗💗 : [바로가기] 💗💗💗💗💗💗💗 : [바로가기]
😚 HIGH CASINO 주의 알림 ➿➿➿➿➿➿➿➿➿ 💗닉네임 : HIGH CASINO 고객센터 💗텔레그렘 ID : @highcs114 💗고유번호 : 8549383086 ➿➿➿➿➿➿➿➿➿ 😚해당 제보 내용 페이백 받아야하는데 벤처리 ❤️블랙리스트 답변 사기,먹튀는 아니나 유저입장에서는 충분히 먹튀라 생각할수 있을듯 한 사례 / 흠..이건 환전이안나온사례도 아니긴하지만 성향이 맞지않다 졸업을 시키는거까지는 알겠는데 유저가 지고있는상황에서 졸업까지하게되면 페이백에 대한 억울함을 있을듯 얼마나될지는모르겠으나 깔끔하게 헤어지는게 맞다 생각합니다 😚 블랙리스트 문의 : [바로가기] 💗💗💗💗💗💗💗 : [바로가기] 💗💗💗💗💗💗💗 : [바로가기]
😚 사기꾼 박제 등록알림 ➿➿➿➿➿➿➿➿➿ 💗닉네임 : black 💗텔레그렘 ID : @blackjang2 💗고유번호 : 8903276255 ➿➿➿➿➿➿➿➿➿ 😚해당 제보 내용 안녕하세요 먹집 제보합니다. 중고 첫콜303만 찍었는데 정산 이래저래 핑계대다가 다음날 대화 밀어버리고 지금도 정상 세탁집인척 홍보하고 다니고 있습니다. 마지막 사진에 콜방이라고 12명있는방에 최근에 블랙 올라온 마닐라OTC 이새끼도 같이 관리자인척 대화하고 그랬던걸보니 한패인것같아요 ❤️블랙리스트 답변 앞전 박제된 마닐라OTC 동일패 혹은 동일인물 추정, 각별히 주의하시길 바랍니다. 😚 블랙리스트 문의 : [바로가기] 💗💗💗💗💗💗💗 : [바로가기] 💗💗💗💗💗💗💗 : [바로가기]
😚 사기꾼 박제 등록알림 ➿➿➿➿➿➿➿➿➿ 💗닉네임 : 천사패드 💗텔레그렘 ID : @ANGELPAD 💗고유번호 : 8732589826 ➿➿➿➿➿➿➿➿➿ 😚해당 제보 내용 개통지연,개바시한다했는데 잠수 ❤️블랙리스트 답변 해당업체는 무기한 영구제휴박탈입니다. 추후해결될시 엄격하게 체크후 진행여부판단 😚 블랙리스트 문의 : [바로가기] 💗💗💗💗💗💗💗 : [바로가기] 💗💗💗💗💗💗💗 : [바로가기]
💗블랙리스트 기간영구제휴 : 우주코인OTC 👾👾👾👾👾👾👾👾👾👾👾 👾 장외거래 [ 우주코인 ] OTC 👾 👾👾👾👾👾👾👾👾👾👾👾 ⭐️ 2️⃣4️⃣시간 상담,출장 ⭐️ 🇺🇿정직,안전,신속 👍 우주OTC ✔️ 인증 제휴업자 ✔️ 🤝 전지역 손대손 🤝 🌹코인 🌹🚑 이체 🌹코인 🌹🚑 현금 🚑현금 🌹🌹코인 🚫이코 불가🚫 ❤️ 전지역 출장비 무료! 👍 365일 24시간 항시대기!
😚 사기꾼 박제 등록알림 ➿➿➿➿➿➿➿➿➿ 💗닉네임 : 마닐라 OTC 💗텔레그렘 ID : @Manila_OTC 💗고유번호 : 8692831609 ➿➿➿➿➿➿➿➿➿ 😚해당 제보 내용 계좌 정태준 국민은행 252525 01 282344 테더 이코 거래한다하고 20먹고 쨈 ❤️블랙리스트 답변 항상 말씀드리는거지만 제일 사기꾼이 많은 업종입니다 주의하시길 바랍니다. 😚 블랙리스트 문의 : [바로가기] 💗💗💗💗💗💗💗 : [바로가기] 💗💗💗💗💗💗💗 : [바로가기]
Showing the 12 most recent of 36 posts we hold for @vsvs1119. 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 — 176,238 of 1,189,255entries 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.
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
Named by 3 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.
Handles this channel named that no longer answer
- Dead references
- 2
- 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
- 2
- vacant every time we have ever looked
@vsvs1119 named 2 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“블랙리스트(SNS사기피해공유)” (@vsvs1119), 55,377 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/vsvs1119.
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.