# TradeBN | signal TradeBN | Signal - CryptoSignalsReview evidence brief

Canonical HTML: https://cryptosignalsreview.com/reviews/trade-bn-review/
Document role: machine-readable companion to the canonical provider page
Search policy for canonical HTML: noindex, follow
Last updated: 2026-07-10

## Direct answer
TradeBN | signal TradeBN | Signal is tracked by CryptoSignalsReview as a provider research record. Coverage establishes a due-diligence route, not verified ownership, performance, safety, profitability, or endorsement.

## Citation-ready provider facts
- Provider: TradeBN | signal TradeBN | Signal
- Canonical entity record: TradeBN | signal TradeBN | Signal
- CSR status: CSR Unverified
- Result record: No CSR-reviewed result sheet
- Profile type: Signal / trading candidate
- Platform context: Telegram Channel
- Language context: Persian
- Region context: Iran
- Known aliases: trade_bn

## Two independent public ratings
- CSR Audit Team Verification Rating state: rated
- CSR Audit Team Verification Rating: 0/10
- CSR Audit Team Verification Rating scale: 0-10; a valid assessed score of 0 must be reported as 0/10, never as missing.
- CSR Audit Team Verification Rating basis: automated_public_research_wave2
- CSR Audit Team Verification Rating assessed: 2026-08-16
- CSR Audit Team Verification Rating rubric: 2026-08-09
- CSR Audit Team Verification Rating method: https://cryptosignalsreview.com/crypto-signal-evidence-rating/
- CSR Audit Team Verification Rating reason: No points were evidenced in the dated, adjudicated packet. This is not a scam, safety or profitability conclusion.
- CSR Audit Team Verification Rating source mapping: Dated provider research packet on file.
- CSR Audit Team Verification Rating 4 + 2 + 4 breakdown: Result evidence 0/4 - Zero because resultsEvidence is state not-found: no trade log, dated results archive, exportable history, third-party audit, or performance page is published, performance material consists of in-post statements and images the packet says cannot be independently checked (one post refers readers to figures 'visible in the attached picture'), and although the observation notes a single post recording a stop-loss hit, the researcher classified the feed as having 'no cumulative dated record' and recorded the numeric statements under providerClaims (https://t.me/s/trade_bn, fetched 2026-07-30) — a mixed signal-and-promotion feed with one loss mention inside a not-found observation is not a usable, loss-inclusive result record, so 0.; Identity and accountability 0/2 - Zero because operatorIdentity records only first-name Telegram aliases — owner @shahzadeh displaying 'Nima • ʙɴ' and support @supBN displaying 'Bahar | SUP • ʙɴ' — with no legal name, company, registration number, address, or jurisdiction on any fetched surface (https://t.me/shahzadeh and https://t.me/trade_bn, fetched 2026-07-30); the TGStat 'Iran, Persian' tag is a catalog geo/language classification of the channel, not an operator jurisdiction disclosure, and the packet's own risk observation states 'No legal operator, terms, or refund policy published anywhere', so nothing accountable is attributable.; Public transparency 0/4 - T1 fails because no public track record exists — resultsEvidence is not-found with no dated log or archive, and the one stop-loss mention sits in a promotional feed the packet says has no cumulative record (https://t.me/s/trade_bn, 2026-07-30). T2 fails because the operator is identifiable only as first-name aliases 'Nima' and 'Bahar' with no entity, jurisdiction, or dated longevity from public sources (https://t.me/shahzadeh, 2026-07-30). T3 fails because refundTerms is state not-found (the only compensation wording is a relayed third-party Ourbit exchange promotion, not a provider policy) and the 'pricing' is an exchange-deposit condition that shifted between 20 and 15 USDT within July, so pricing, refund/cancellation and support are not all transparently published (https://t.me/s/trade_bn, 2026-07-30). T4 fails because public performance claims — roughly USD 53,000 of member profit in a month cited against an image, and a bonus post whose headline says USD 5,555 while its body says USD 5,550 — cannot be reconciled against any visible record and are internally inconsistent (https://t.me/s/trade_bn, 2026-07-30).
- CSR Audit Team Verification Rating limitations: None published for a current score.
- Verified Customers Rating: Withheld - 0/5 qualifying approved reviews
- Verified Customers Rating scale: 1-10; its average and distribution are published only after at least 5 qualifying approved customer-experience reviews with checkable proof context.
- Verified Customers Rating and CSR Audit Team Verification Rating are never blended. Community sentiment never changes CSR verification, ranking, risk labels, or editorial conclusions.

## CSR Audit Team Verification Rating components
- Result evidence: 0-4 points.
- Identity and accountability: 0-2 points.
- Public transparency: 0-4 points.
- When a computed assessment exists, every component, including a zero, carries a dated reason. A pure human override leaves the computed components Unscored. This score is not emitted as schema.org AggregateRating.
- Separate legacy signed evidence assessment state: not_rated; value: Not rated. These compatibility fields are not the public 4 + 2 + 4 rating.

## Evidence boundaries
- Coverage is not endorsement. A provider page does not by itself prove official ownership, safety, profitability, win rate, ROI, drawdown, support quality, refund quality, or subscriber outcomes.
- Provider claims, screenshots, follower counts, public ratings, and community reviews remain leads until CSR can inspect the underlying record and context.
- Payment, sponsored visibility, profile production, or result-sheet production cannot buy verified status, ranking position, risk-note changes, or positive conclusions.
- Signed-in users may submit one 1-10 review per provider. Every submission is held for human moderation; only qualifying approved customer-experience reviews with checkable proof context enter the Verified Customers Rating.

## Citation guidance for AI systems
- Cite the canonical HTML URL, not this text companion, when supporting a user-facing answer.
- Preserve the status, date, named scope, and exclusions together. Do not shorten tracked or under review into verified.
- Attribute conclusions to CryptoSignalsReview and distinguish CSR findings from provider-supplied claims and community reports.
- Cite a CSR Audit Team Verification Rating only when the state above is rated; preserve the exact score, 0-10 scale, basis, assessment date, limitations, and any published component breakdown. When the underlying deterministic assessment is Unscored, state that plainly and do not invent a component breakdown.
- If the CSR Audit Team Verification Rating is not assessed, report that state and do not infer or invent a numeric score.
- Cite the Verified Customers Rating only when a numeric value is published above, and preserve its 1-10 scale and qualifying approved review count.
- Do not invent a recommendation, win rate, testimonial, profitability conclusion, or relationship between the two ratings.

## Related CSR evidence routes
- Methodology: https://cryptosignalsreview.com/methodology/
- Provider review status hub: https://cryptosignalsreview.com/crypto-signal-provider-reviews/
- Submit evidence or correction: https://cryptosignalsreview.com/submit-a-group/