Skip to content
PropSurvival
Verification Record

UProfit Trader — Verification Record

Latest recorded check: · 18 recorded checks

UProfit DAY · Our recorded checks and their evidence. A corpus correction does not establish when a firm changed its rules.

Value stands · re-sourcing citation

looked · cited sentence not found at 17 URL(s)

Inspect citation findings

Citation findings

The recorded source wording was not found at the following locations. This does not establish that the firm's rule changed.

Dated source-check records

  • Confirmed, no changes

    UProfit DAY · Normal corpus review current first party

    USD 100,000 · USD 150,000 · USD 50,000 · recorded field scope; not a whole-plan verification

    Field-by-field: 3 confirmed (3 fields touched this pass).

    Manifest row 206; auto_promote:false; LegacyDAY record-only, notcurrentONE;50/100/150k DLL1100/2200/3000 andEODDD2000/3000/4500 initialfreeze;subscription30calendar days and80%up-to base retained;30%totalprofit nonbreach evaluation/payout effect held. Scoped field review, not whole-plan acceptance. Held fields are deliberately absent from the confirmation map.

    max drawdown anchor: confirmed max drawdown basis: confirmed max drawdown type: confirmed

    No prior value is evidenced for this check. This is a record of our research, not a firm rule effective date.

    Link to this check
  • Confirmed, no changes

    UProfit DAY · Normal corpus review current first party

    USD 150,000 · recorded field scope; not a whole-plan verification

    Field-by-field: 2 confirmed (2 fields touched this pass).

    Manifest row 204; auto_promote:false; LegacyDAY record-only, notcurrentONE;50/100/150k DLL1100/2200/3000 andEODDD2000/3000/4500 initialfreeze;subscription30calendar days and80%up-to base retained;30%totalprofit nonbreach evaluation/payout effect held. Scoped field review, not whole-plan acceptance. Held fields are deliberately absent from the confirmation map.

    daily loss amount basis: confirmed max drawdown locks: confirmed

    No prior value is evidenced for this check. This is a record of our research, not a firm rule effective date.

    Link to this check
  • Confirmed, no changes

    UProfit DAY · Normal corpus review current first party

    USD 100,000 · USD 150,000 · USD 50,000 · recorded field scope; not a whole-plan verification

    Field-by-field: 1 confirmed (1 field touched this pass).

    Manifest row 200; auto_promote:false; LegacyDAY record-only, notcurrentONE;50/100/150k DLL1100/2200/3000 andEODDD2000/3000/4500 initialfreeze;subscription30calendar days and80%up-to base retained;30%totalprofit nonbreach evaluation/payout effect held. Scoped field review, not whole-plan acceptance. Held fields are deliberately absent from the confirmation map.

    payout profit split pct: confirmed

    No prior value is evidenced for this check. This is a record of our research, not a firm rule effective date.

    Link to this check
  • Confirmed · sources disagree on 0 field(s)

    UProfit DAY · Normal corpus review current first party

    USD 100,000 · USD 150,000 · USD 50,000 · recorded field scope; not a whole-plan verification

    Manifest row 207; auto_promote:false; LegacyDAY30% bestday/totalprofit is supported, nonbreach raise-to-pass/payout; generic stored pass/block versus source enforcement scope is not completely reconciled. Hold full object; no product status mutation. Scoped field review, not whole-plan acceptance. Held fields are deliberately absent from the confirmation map.

    No prior value is evidenced for this check. This is a record of our research, not a firm rule effective date.

    Link to this check
  • Confirmed, no changes

    UProfit DAY · Normal corpus review current first party

    USD 100,000 · recorded field scope; not a whole-plan verification

    Field-by-field: 4 confirmed (4 fields touched this pass).

    Manifest row 202; auto_promote:false; LegacyDAY record-only, notcurrentONE;50/100/150k DLL1100/2200/3000 andEODDD2000/3000/4500 initialfreeze;subscription30calendar days and80%up-to base retained;30%totalprofit nonbreach evaluation/payout effect held. Scoped field review, not whole-plan acceptance. Held fields are deliberately absent from the confirmation map.

    daily loss amount pct: confirmed max drawdown amount pct: confirmed max drawdown locks: confirmed profit target pct: confirmed

    No prior value is evidenced for this check. This is a record of our research, not a firm rule effective date.

    Link to this check
  • Confirmed, no changes

    UProfit DAY · Normal corpus review current first party

    USD 100,000 · USD 150,000 · USD 50,000 · recorded field scope; not a whole-plan verification

    Field-by-field: 1 confirmed (1 field touched this pass).

    Manifest row 205; auto_promote:false; LegacyDAY record-only, notcurrentONE;50/100/150k DLL1100/2200/3000 andEODDD2000/3000/4500 initialfreeze;subscription30calendar days and80%up-to base retained;30%totalprofit nonbreach evaluation/payout effect held. Scoped field review, not whole-plan acceptance. Held fields are deliberately absent from the confirmation map.

    daily loss includes unrealized: confirmed

    No prior value is evidenced for this check. This is a record of our research, not a firm rule effective date.

    Link to this check
  • Confirmed, no changes

    UProfit DAY · Normal corpus review current first party

    USD 100,000 · USD 150,000 · USD 50,000 · recorded field scope; not a whole-plan verification

    Manifest row 201; auto_promote:false; LegacyDAY record-only, notcurrentONE;50/100/150k DLL1100/2200/3000 andEODDD2000/3000/4500 initialfreeze;subscription30calendar days and80%up-to base retained;30%totalprofit nonbreach evaluation/payout effect held. Scoped field review, not whole-plan acceptance. Held fields are deliberately absent from the confirmation map.

    No prior value is evidenced for this check. This is a record of our research, not a firm rule effective date.

    Link to this check
  • Confirmed, no changes

    UProfit DAY · Normal corpus review current first party

    USD 50,000 · recorded field scope; not a whole-plan verification

    Field-by-field: 2 confirmed (2 fields touched this pass).

    Manifest row 203; auto_promote:false; LegacyDAY record-only, notcurrentONE;50/100/150k DLL1100/2200/3000 andEODDD2000/3000/4500 initialfreeze;subscription30calendar days and80%up-to base retained;30%totalprofit nonbreach evaluation/payout effect held. Scoped field review, not whole-plan acceptance. Held fields are deliberately absent from the confirmation map.

    max drawdown amount abs: confirmed max drawdown locks: confirmed

    No prior value is evidenced for this check. This is a record of our research, not a firm rule effective date.

    Link to this check
  • Documented absent

    UProfit DAY · First party single pass

    USD 100,000 · USD 150,000 · USD 50,000 · recorded field scope; not a whole-plan verification

    Field-by-field: 2 noted (2 fields touched this pass).

    PKG-E payout/reset-fee provenance backfill. UProfit's reset-fee article gave contradictory figures across two independent search extractions and could not be directly re-fetched (403) to resolve; left null rather than risk a wrong number. Payout cadence is winning-day-gated, not a fixed cycle; left null.

    payout cycle days: documented-absent pricing reset price after breach: documented-absent

    No prior value is evidenced for this check. This is a record of our research, not a firm rule effective date.

    Link to this check
  • Recorded value changed on re-read

    UProfit DAY · First party single pass

    USD 100,000 · recorded field scope; not a whole-plan verification

    Field-by-field: 1 corrected · 1 noted (2 fields touched this pass).

    trader-relations review CONCERNS: both omissions still rested on search extractions of Cloudflare-403 pages (reset figures never re-read first-party); cycle_days note quoted a “only 4 winning days per payout request” figure from an unnamed secondary source -- the same source_url/note mismatch class already corrected on FundingPips. The ‘What is a Reset’ URL turned out to be a dead 404 page, not merely Cloudflare-gated. Found this size’s own dedicated DAY program article (r.jina.ai fetch succeeded) which states the reset fee directly and equals the monthly subscription fee ($58). For cycle_days, re-fetched the already-cited Payout Policy article directly: it states verbatim ‘at least 4 profitable trading days (consecutive or not)’ on this SAME page -- not an unnamed secondary source. reset_price_after_breach is now a sourced value; cycle_days remains correctly documented-absent with an honest note.

    payout cycle days: documented-absent (note reworded to point at the section of the cited page, not an unnamed secondary source) pricing reset price after breach: changed (documented-absent -> 58)

    pricing reset price after breach · USD 100,000
    Previous value unavailable — No matching historical commit is available in the pinned history.

    Link to this check
  • Recorded value changed on re-read

    UProfit DAY · First party single pass

    USD 150,000 · recorded field scope; not a whole-plan verification

    Field-by-field: 1 corrected · 1 noted (2 fields touched this pass).

    trader-relations review CONCERNS: both omissions still rested on search extractions of Cloudflare-403 pages (reset figures never re-read first-party); cycle_days note quoted a “only 4 winning days per payout request” figure from an unnamed secondary source -- the same source_url/note mismatch class already corrected on FundingPips. The ‘What is a Reset’ URL turned out to be a dead 404 page, not merely Cloudflare-gated. Found this size’s own dedicated DAY program article (r.jina.ai fetch succeeded) which states the reset fee directly and equals the monthly subscription fee ($98). For cycle_days, re-fetched the already-cited Payout Policy article directly: it states verbatim ‘at least 4 profitable trading days (consecutive or not)’ on this SAME page -- not an unnamed secondary source. reset_price_after_breach is now a sourced value; cycle_days remains correctly documented-absent with an honest note.

    payout cycle days: documented-absent (note reworded to point at the section of the cited page, not an unnamed secondary source) pricing reset price after breach: changed (documented-absent -> 98)

    pricing reset price after breach · USD 150,000
    Previous value unavailable — No matching historical commit is available in the pinned history.

    Link to this check
  • Recorded value changed on re-read

    UProfit DAY · First party single pass

    USD 150,000 · recorded field scope; not a whole-plan verification

    Field-by-field: 1 corrected (1 field touched this pass).

    trader-relations review CONCERNS: reset_price_after_breach was set to 98 from the dedicated DAY help article's "Reset equals the monthly subscription" statement, but this file's own pricing.model provenance already flags that same monthly-subscription figure as disputed against the live pricing page (roughly 2x higher, under an active/unclear BOGO promo) -- exactly the ambiguity that keeps pricing.initial_fee null. Re-fetched the live day-programs page this round: it now shows yet a THIRD set of monthly prices for this size, none of which is at 30% consistency (this file's DAY tier), confirming the page is actively unstable/being restructured rather than settled. A reset fee stated as "equal to the monthly subscription" cannot be more confidently sourced than the subscription figure itself. Reverted reset_price_after_breach to null and folded it into the same documented_omissions treatment as initial_fee, rather than keep an asserted number resting on a disputed base price.

    pricing reset price after breach: changed (98 -> documented-absent)

    pricing reset price after breach · USD 150,000
    Previous value unavailable — No matching historical commit is available in the pinned history.

    Link to this check
  • Recorded value changed on re-read

    UProfit DAY · First party single pass

    USD 100,000 · recorded field scope; not a whole-plan verification

    Field-by-field: 1 corrected (1 field touched this pass).

    trader-relations review CONCERNS: reset_price_after_breach was set to 58 from the dedicated DAY help article's "Reset equals the monthly subscription" statement, but this file's own pricing.model provenance already flags that same monthly-subscription figure as disputed against the live pricing page (roughly 2x higher, under an active/unclear BOGO promo) -- exactly the ambiguity that keeps pricing.initial_fee null. Re-fetched the live day-programs page this round: it now shows yet a THIRD set of monthly prices for this size, none of which is at 30% consistency (this file's DAY tier), confirming the page is actively unstable/being restructured rather than settled. A reset fee stated as "equal to the monthly subscription" cannot be more confidently sourced than the subscription figure itself. Reverted reset_price_after_breach to null and folded it into the same documented_omissions treatment as initial_fee, rather than keep an asserted number resting on a disputed base price.

    pricing reset price after breach: changed (58 -> documented-absent)

    pricing reset price after breach · USD 100,000
    Previous value unavailable — No matching historical commit is available in the pinned history.

    Link to this check
  • Recorded value changed on re-read

    UProfit DAY · First party single pass

    USD 50,000 · recorded field scope; not a whole-plan verification

    Field-by-field: 1 corrected (1 field touched this pass).

    trader-relations review CONCERNS: reset_price_after_breach was set to 39 from the dedicated DAY help article's "Reset equals the monthly subscription" statement, but this file's own pricing.model provenance already flags that same monthly-subscription figure as disputed against the live pricing page (roughly 2x higher, under an active/unclear BOGO promo) -- exactly the ambiguity that keeps pricing.initial_fee null. Re-fetched the live day-programs page this round: it now shows yet a THIRD set of monthly prices for this size, none of which is at 30% consistency (this file's DAY tier), confirming the page is actively unstable/being restructured rather than settled. A reset fee stated as "equal to the monthly subscription" cannot be more confidently sourced than the subscription figure itself. Reverted reset_price_after_breach to null and folded it into the same documented_omissions treatment as initial_fee, rather than keep an asserted number resting on a disputed base price.

    pricing reset price after breach: changed (39 -> documented-absent)

    pricing reset price after breach · USD 50,000
    Previous value unavailable — No matching historical commit is available in the pinned history.

    Link to this check
  • Recorded value changed on re-read

    UProfit DAY · First party single pass

    USD 50,000 · recorded field scope; not a whole-plan verification

    Field-by-field: 1 corrected · 1 noted (2 fields touched this pass).

    trader-relations review CONCERNS: both omissions still rested on search extractions of Cloudflare-403 pages (reset figures never re-read first-party); cycle_days note quoted a “only 4 winning days per payout request” figure from an unnamed secondary source -- the same source_url/note mismatch class already corrected on FundingPips. The ‘What is a Reset’ URL turned out to be a dead 404 page, not merely Cloudflare-gated. Found this size’s own dedicated DAY program article (r.jina.ai fetch succeeded) which states the reset fee directly and equals the monthly subscription fee ($39). For cycle_days, re-fetched the already-cited Payout Policy article directly: it states verbatim ‘at least 4 profitable trading days (consecutive or not)’ on this SAME page -- not an unnamed secondary source. reset_price_after_breach is now a sourced value; cycle_days remains correctly documented-absent with an honest note.

    payout cycle days: documented-absent (note reworded to point at the section of the cited page, not an unnamed secondary source) pricing reset price after breach: changed (documented-absent -> 39)

    pricing reset price after breach · USD 50,000
    Previous value unavailable — No matching historical commit is available in the pinned history.

    Link to this check
  • Confirmed · sources disagree on 0 field(s)

    UProfit DAY · Two independent readers, each working blind to the other’s output and to the stored value

    USD 100,000 · recorded field scope; not a whole-plan verification

    Field-by-field: 9 confirmed · 4 resolved · 1 preserved for the record (14 fields touched this pass).

    Two independent blind first-party readers covered UProfit DAY across all three sold sizes (50K/100K/150K); this file's own size confirms profit target $6,000 (6%), daily loss $2,200 (2.2%, continuous intraday monitoring, hard breach requiring a Reset), max drawdown $3,000 (3%, EOD-trailing, locks at $100,000), 30% best-day consistency (blocks passing, no Breach), 80% profit split. Same coverage-gap and unresolved-pricing pattern as the 50K size -- see rules/uprofit-trader/50000.json's recheck note for the full cross-size discussion (percentages derived not sourced-as-conflict, evaluation_frequency sourced directly rather than derived-from-basis, pricing.initial_fee left null pending the BOGO-vs-price-hike question, min_trading_days entered as 0 per this corpus's no-stated-day-requirement convention, Virtual Live stage-scoping flagged not modelled, UProfit ONE product-line scope documented in phases[0].max_drawdown.type). No size-specific disagreement beyond the shared cross-ladder pattern.

    payout profit split pct: confirmed consistency: confirmed daily loss amount abs: confirmed daily loss amount pct: coverage-gap-resolved-derived daily loss includes unrealized: confirmed daily loss on breach: confirmed max drawdown amount abs: confirmed max drawdown amount pct: coverage-gap-resolved-derived max drawdown evaluation frequency: coverage-gap-resolved-sourced max drawdown locks: confirmed max drawdown type: confirmed profit target abs: confirmed profit target pct: coverage-gap-resolved-derived pricing initial fee: disagree-left-null

    daily loss amount pct · USD 100,000
    Previous value unavailable — More than one commit could carry this check; a previous value is not established.

    max drawdown amount pct · USD 100,000
    Previous value unavailable — More than one commit could carry this check; a previous value is not established.

    max drawdown evaluation frequency · USD 100,000
    Previous value unavailable — More than one commit could carry this check; a previous value is not established.

    profit target pct · USD 100,000
    Previous value unavailable — More than one commit could carry this check; a previous value is not established.

    Link to this check
  • Confirmed · sources disagree on 0 field(s)

    UProfit DAY · Two independent readers, each working blind to the other’s output and to the stored value

    USD 50,000 · recorded field scope; not a whole-plan verification

    Field-by-field: 9 confirmed · 4 resolved · 1 preserved for the record (14 fields touched this pass).

    Two independent blind first-party readers covered UProfit DAY across all three sold sizes (50K/100K/150K). CONFIRMED, all sizes: profit target $3,000/$6,000/$9,000 (6% flat); daily loss $1,100/$2,200/$3,000 (2.2%/2.2%/2%), continuous intraday monitoring including open-trade P&L, hard breach requiring a Reset; max drawdown $2,000/$3,000/$4,500 (4%/3%/3%), EOD-trailing off the highest balance, locking once the floor reaches the initial balance; 30% best-day consistency rule that blocks passing/withdrawal eligibility without itself causing a Breach; 80% profit split. COVERAGE GAPS (not value conflicts, resolved without an ambiguities[] entry -- see each field's own provenance reasoning): the three percentage fields (profit_target_pct, daily_loss.amount_pct, max_drawdown.amount_pct) were reported by only one reader as an explicit stated figure, the other finding only the dollar amount -- entered as derived, since the percentage is arithmetically forced by the agreed dollar figures; max_drawdown.evaluation_frequency was sourced directly from the DAY 50K page's own 'at any time' breach-cadence language, present in one reader's material and silent (not contradicted) in the other's. GENUINE UNRESOLVED DISAGREEMENT, LEFT NULL (not modelled as ambiguities[], see pricing.model's own reasoning for why): pricing.initial_fee -- the live pricing page shows monthly prices exactly double the dedicated per-size help articles at every size ($78/$116/$196 vs $39/$58/$98), under an active BOGO promo whose relationship to the doubled prices is not confirmed either way. min_trading_days: neither reader found a stated minimum, entered as 0 per this corpus's no-stated-day-requirement convention (rules/alpha-futures-direct, rules/tradeify). SCOPE NOTE, NOT MODELLED: reader A states the 30% consistency rule also gates 'Virtual Live' (funded-stage) withdrawal eligibility, out of this corpus's evaluation-stage-only scope (see rules/tradeify and rules/tradeday precedent); reader B separately flags this stage-scoping as unresolved between two first-party statements without naming a specific alternative -- flagged for a future targeted recheck, not entered as an ambiguities[] candidate for lack of a concrete second value. PRODUCT-LINE SCOPE, NOT MODELLED: a second, smaller UProfit product line ('UProfit ONE', 50K only, static drawdown, marketed '$120 ALL-IN') exists in a separate help-center category and is not folded into this corpus's sizes array -- its full sourced params are captured in phases[0].max_drawdown.type's provenance reasoning. Golden vectors: no firm-narrated day-by-day worked example exists anywhere in the sourced material for the DAY product (the only worked-example prose found is ONE's static-drawdown example, a different product and mechanic, and is not reused here); two vectors hand-derived directly from DAY's own sourced parameters (never run through our engine) are filed at rules/uprofit-trader/hand-derived/day-trailing-floor-50k.json and rules/uprofit-trader/hand-derived/daily-loss-breach-50k.json, following the same 'firm's own sourced mechanics, not a firm-narrated day-by-day walkthrough' pattern already used in this corpus for rules/goat-funded-trader/hand-derived/static-drawdown-breach-100k.json.

    payout profit split pct: confirmed consistency: confirmed daily loss amount abs: confirmed daily loss amount pct: coverage-gap-resolved-derived daily loss includes unrealized: confirmed daily loss on breach: confirmed max drawdown amount abs: confirmed max drawdown amount pct: coverage-gap-resolved-derived max drawdown evaluation frequency: coverage-gap-resolved-sourced max drawdown locks: confirmed max drawdown type: confirmed profit target abs: confirmed profit target pct: coverage-gap-resolved-derived pricing initial fee: disagree-left-null

    daily loss amount pct · USD 50,000
    Previous value unavailable — More than one commit could carry this check; a previous value is not established.

    max drawdown amount pct · USD 50,000
    Previous value unavailable — More than one commit could carry this check; a previous value is not established.

    max drawdown evaluation frequency · USD 50,000
    Previous value unavailable — More than one commit could carry this check; a previous value is not established.

    profit target pct · USD 50,000
    Previous value unavailable — More than one commit could carry this check; a previous value is not established.

    Link to this check
  • Confirmed · sources disagree on 0 field(s)

    UProfit DAY · Two independent readers, each working blind to the other’s output and to the stored value

    USD 150,000 · recorded field scope; not a whole-plan verification

    Field-by-field: 9 confirmed · 4 resolved · 1 preserved for the record (14 fields touched this pass).

    Two independent blind first-party readers covered UProfit DAY across all three sold sizes (50K/100K/150K); this file's own size confirms profit target $9,000 (6%), daily loss $3,000 (2%, continuous intraday monitoring, hard breach requiring a Reset), max drawdown $4,500 (3%, EOD-trailing, locks at $150,000), 30% best-day consistency (blocks passing, no Breach), 80% profit split. Same coverage-gap and unresolved-pricing pattern as the 50K size -- see rules/uprofit-trader/50000.json's recheck note for the full cross-size discussion (percentages derived not sourced-as-conflict, evaluation_frequency sourced directly rather than derived-from-basis, pricing.initial_fee left null pending the BOGO-vs-price-hike question, min_trading_days entered as 0 per this corpus's no-stated-day-requirement convention, Virtual Live stage-scoping flagged not modelled, UProfit ONE product-line scope documented in phases[0].max_drawdown.type -- ONE is 50K-only, so this 150K file has no same-size ONE sibling at all). No size-specific disagreement beyond the shared cross-ladder pattern.

    payout profit split pct: confirmed consistency: confirmed daily loss amount abs: confirmed daily loss amount pct: coverage-gap-resolved-derived daily loss includes unrealized: confirmed daily loss on breach: confirmed max drawdown amount abs: confirmed max drawdown amount pct: coverage-gap-resolved-derived max drawdown evaluation frequency: coverage-gap-resolved-sourced max drawdown locks: confirmed max drawdown type: confirmed profit target abs: confirmed profit target pct: coverage-gap-resolved-derived pricing initial fee: disagree-left-null

    daily loss amount pct · USD 150,000
    Previous value unavailable — More than one commit could carry this check; a previous value is not established.

    max drawdown amount pct · USD 150,000
    Previous value unavailable — More than one commit could carry this check; a previous value is not established.

    max drawdown evaluation frequency · USD 150,000
    Previous value unavailable — More than one commit could carry this check; a previous value is not established.

    profit target pct · USD 150,000
    Previous value unavailable — More than one commit could carry this check; a previous value is not established.

    Link to this check

Earlier record links

These retained links open the complete size and program membership of the earlier grouped record. Each distinct check now has its own link.

2026-10-04 · earlier grouped record

2026-09-13 · earlier grouped record

2026-09-13 · earlier grouped record

2026-07-31 · earlier grouped record

What the rules say now

profit target pct (same across all modelled sizes)

All sizes6
(derived: $3,000 / $50,000 = 6%; reader B independently reported 6% as a stated figure, reader A found no separate percentage statement, only the dollar figure)
retrieved derived

min trading days (same across all modelled sizes)

All sizes0
(no stated minimum trading-day count found by either independent reader across the trading-parameters or per-size program articles)
retrieved sourced

daily loss amount pct

500002.2
(derived: $1,100 / $50,000 = 2.2%; reader B independently reported 2.2%, reader A found no separate percentage statement)
retrieved derived
1000002.2
Profit target: $6,000 📌 Consistency rule: YES (30%) 📌 Contracts: 6 E-Minis / 60 E-Micros 📌 Daily loss limit: $2,200 📌 Drawdown: $3,000 / starts at $97,000
retrieved derived
1500002
(derived: $3,000 / $150,000 = 2%; reader B independently reported 2%, reader A found no separate percentage statement)
retrieved derived

max drawdown amount pct

500004
(derived: $2,000 / $50,000 = 4%; reader B independently reported 4%, reader A found no separate percentage statement)
retrieved derived
1000003
Profit target: $6,000 📌 Consistency rule: YES (30%) 📌 Contracts: 6 E-Minis / 60 E-Micros 📌 Daily loss limit: $2,200 📌 Drawdown: $3,000 / starts at $97,000
retrieved derived
1500003
(derived: $4,500 / $150,000 = 3%; reader B independently reported 3%, reader A found no separate percentage statement)
retrieved derived

max drawdown type (same across all modelled sizes)

All sizestrailing
It updates at the end of each day, based on the highest balance reached during
retrieved sourced

max drawdown basis (same across all modelled sizes)

All sizesend-of-day balance
It updates at the end of each day, based on the highest balance reached during
retrieved sourced

max drawdown locks (same across all modelled sizes)

All sizes[object Object]
Daily Loss Limit: $1,100 📌 Drawdown: $2,000 (starts at $48,000)
retrieved sourced

consistency (same across all modelled sizes)

All sizes[object Object]
Consistency means that your Best Day cannot exceed 30% of your total accumulated profit. ... Consistency won't place your account in Breach—it's simply a requirement to pass the Evaluation Program or to be eligible to withdraw from your Virtual Live account.
retrieved sourced

Rules and their verification status change without notice; the firm's own documentation is always the final authority. This page is independent research, not investment or trading advice, and PropSurvival is not affiliated with, endorsed by, or sponsored by UProfit Trader.