Drakor
- Эксперты
-
Oguzhan Senturk
Algorithmic Trading Systems Developer
I develop automated trading systems and risk-control tools for MetaTrader 5. I do not see a trading system as a strategy alone. Research, order execution, position management, account protection and the user interface all need to work as one coherent system. - Версия: 1.1
- Обновлено: 16 сентября 2026
- Активации: 10
DRAKOR is a dual-market MetaTrader 5 Expert Advisor for BTCUSD and USDJPY. It runs two independent engines from one chart, using completed H1 data and broker-side stop losses. The engines share no signal, position or risk budget, so the product combines two different markets rather than duplicating one strategy.
DRAKOR uses no grid, martingale, averaging down or recovery sizing. It contains no DLL, news feed or external data file. Position size is calculated separately for each engine from the working capital allocated by the user.
Historical Strategy Tester results, not live trading results. The figures below were measured on two independent broker feeds from August 2018 to July 2026 with the same settings.
AT A GLANCE
| Markets | BTCUSD and USDJPY |
| Structure | Two independent engines on one account |
| Signal timeframe | Completed H1 bars |
| Reference allocation | 10,000 account-currency units |
| Supported allocation range | 2,500 to 1,000,000 |
| Position protection | Broker-side stop loss on every accepted entry |
| Account type | Hedging and netting supported |
TWO REFERENCE FEEDS
The same product logic, inputs, period and account settings were measured on IC Markets SC and Pepperstone. Publishing both results shows the effect of different quotes, spreads, sessions and execution instead of relying on one favourable feed.
| Reference feed | Closing balance | Equity DD Relative | Profit factor | Trades |
| IC Markets SC | 194,957.33 USD | 19.86% | 1.26 | 2,683 |
| Pepperstone | 107,928.08 USD | 21.21% | 1.22 | 2,690 |
Both tests started with 10,000 USD. These are historical measurements for the named feeds and dates, not forecasts. The difference between the two results is important: broker data and BTCUSD trading costs materially affect the outcome.
BROKER AND SYMBOL REQUIREMENTS
The published record requires both BTCUSD and USDJPY. DRAKOR automatically prefers an exact symbol name and can resolve common broker prefixes or suffixes. If it cannot find a configured market, that engine switches off and clearly reports the missing symbol; the other engine continues if its market exists. If neither exists, DRAKOR opens no position.
| Requirement | Reason |
| Tradeable BTCUSD and USDJPY | Each engine trades its own measured market; both are required to reproduce the combined record |
| Complete H1 history for both | Partial history produces fewer signals and a different curve |
| Competitive BTCUSD spread | BTCUSD is the dominant cost; a RAW or ECN low-spread account is preferred |
| Leverage 1:100 or higher | Used for both published reference tests |
| Minimum allocation 2,500 | Below this level the broker minimum lot can exceed the configured risk |
Run DRAKOR in your own broker's Strategy Tester before use. Quotes, commission, swap, contract size, volume limits, sessions and execution are broker-specific.
WORKING CAPITAL
InpWorkingCapital defines the virtual allocation assigned to DRAKOR. For example, entering 5,000 on a larger account makes lot sizing, Working Now and DRAKOR's safety brakes follow that allocation instead of the full account balance. Manual trades and other EAs are excluded from this internal path.
| Allocation | Measured behaviour |
| 2,500 | Supported minimum. Entries that exceed risk because of the broker minimum lot are skipped |
| 10,000 | Reference allocation behind every headline result on this page |
| Up to 1,000,000 | Supported input maximum; actual capacity depends on the broker's BTCUSD volume limits |
IC Markets retained near-linear sizing to 1,000,000 in the measured capacity test. On Pepperstone, the BTCUSD volume cap began restricting full target size above roughly 60,000. This is a broker-capacity boundary, not a promise that every account size will reproduce the reference curve.
RISK AND EXECUTION
- BTCUSD and USDJPY have separate symbols, positions, magic numbers and risk inputs.
- Every accepted order is submitted with a broker-side stop loss.
- Volume is never rounded upward. An entry is skipped if the minimum lot would exceed the configured risk.
- Trading session, spread limit, volume step, stop distance, free margin and order result are checked before execution.
- DRAKOR manages only positions carrying its own magic numbers.
- Optional session-drawdown, daily-loss and spread brakes can block new entries.
The reference configuration uses a 25% maximum session-drawdown brake. On a live chart, a triggered brake closes DRAKOR-owned positions and remains latched until the account is reviewed and START is pressed again. In Strategy Tester it reports the event and re-arms so the full historical period can continue.
NORMAL OPERATING BEHAVIOUR
| Measurement | Reference observation |
| Average entry frequency | Approximately 28 per month across both engines |
| Monthly range | 18 entries in the quietest month, 37 in the busiest |
| Longest period without a new position | Just under six days |
| Winning trades | 38.35% |
| Longest losing sequence | 15 trades |
Losing trades are frequent by design. The measured engine depended on the average winner being larger than the average loser rather than on a high win rate. Quiet periods and losing sequences within this range are not, by themselves, evidence that the product has stopped working.
PANEL AND OPERATION
DRAKOR starts in a waiting state. START permits new entries after the checks pass; STOP blocks new entries while existing DRAKOR positions remain protected and managed until closure.
The English and Turkish panel shows the state and resolved symbol of both engines, owned positions, current spread, account equity, allocated capital, Working Now and session drawdown. Contextual help and a five-page guide are built in.
Attaching DRAKOR to a second chart transfers ownership and prevents two active copies on the same account. Applying a chart template unloads the EA; reattach it after changing a template. Broker-side stops remain active during a terminal disconnection, but timed exit management requires the terminal and DRAKOR to be running.
HOW TO REPRODUCE THE REFERENCE TEST
| Chart symbol | BTCUSD |
| Chart period | H1 |
| Date range | 2018.08.01 – 2026.07.01 |
| Initial deposit | 10,000 USD |
| Leverage | 1:100 |
| Modelling | Every tick based on real ticks, or the highest-quality model available |
| Inputs | Defaults, with InpWorkingCapital set to 10,000 |
Allow complete H1 history to download for both symbols before starting. Compare Equity Drawdown Relative and trade count as well as ending balance. A different broker is expected to produce different figures because the two engines act on that broker's own historical bars and costs.
The reference report shows 88% History Quality on IC Markets and 87% on Pepperstone because BTCUSD tick history does not extend as far back as major-currency history. A separate one-minute OHLC control produced a higher balance and slightly lower drawdown, so the figures above use the more conservative model result and do not depend on fine tick sequencing.
DEVELOPMENT AND VERIFICATION
The two shipped engines remained after research across thousands of measured tests and multiple market families. Surviving candidates were checked with permutation tests, random-trigger controls, look-ahead audits, non-overlapping samples, block bootstrap, neighbouring-parameter tests and cost/slippage stress.
Both engines were then measured on two independent broker feeds. Their monthly relationship and joint drawdown behaviour were checked before they were combined. Capital tests from 2,500 to 1,000,000 identified where minimum lot, margin or broker volume limits become the binding constraint.
The shipping binary was exercised in a final full-period reference test, while the same source was separately verified on the second feed. The reported figures were regenerated from retained MetaTrader reports. These controls reduce avoidable research and release errors; they do not guarantee future performance.
INTRODUCTORY PRICING AND RENTAL
DRAKOR is currently offered at an introductory permanent-license price of 99 USD. The planned campaign increases the price by 50 USD after each completed sale, toward a planned regular price of 799 USD. The price displayed by MQL5 at the time of purchase is the applicable price.
A fully featured one-month rental at 49 USD is available for the first 20 rentals. After the twentieth rental, the rental campaign will be removed and DRAKOR will remain available by permanent purchase.
SUPPORT AND RISK
For support, contact the developer through MQL5 and include the broker/server, account type, exact symbol names, Inputs screenshot and relevant Journal lines.
Risk warning: Trading foreign exchange, cryptocurrency and CFDs involves substantial risk. All figures above are historical MetaTrader 5 Strategy Tester measurements and are not live trading results. Past performance is not indicative of future results. Broker conditions can materially change performance, stops cannot eliminate gap or slippage losses, and no system guarantees a result. Do not trade with capital you cannot afford to lose.
