Fetching the page
Fetching the page
Transparency report
Every figure below was counted by a database from its own records of this calendar month (UTC). Nothing on this page was written by hand, and the words are the same for every month.
Complete month
Counted . Asked again about every ten minutes.
Execution
| Instrument group | Orders filled | Filled at the price on screen | Better | Worse | Median slippage, points | 95th percentile, points | Median fill time | 95th percentile |
|---|---|---|---|---|---|---|---|---|
| No order was filled on live accounts in this month. 0 orders, so there is nothing to measure. | ||||||||
A demo order is filled by GIO4X’s own demo engine at a simulated price, not a market price. These figures describe how the demo behaves and are not a measure of live execution.
| Instrument group | Orders filled | Filled at the price on screen | Better | Worse | Median slippage, points | 95th percentile, points | Median fill time | 95th percentile |
|---|---|---|---|---|---|---|---|---|
| Forex | 2 | not recorded | not recorded | |||||
| Indices | 1 | not recorded | not recorded | |||||
| All groups | 3 | not recorded | not recorded | |||||
SimulationSource: 777 Raptor demo engineDemo fills only. Simulated prices are not market prices.
Counted by the terminal’s database from the orders it recorded as filled in the month, by the UTC time of the fill. Slippage is the fill price against the price the client’s terminal sent with a market order, in points; a positive figure is worse for the client. Fill time is from GIO4X’s server receiving a market order to the fill being recorded. A statistic made from fewer than 20 orders is not published and its count is shown instead; “not recorded” means no order in the cell carries the value. The method in full is on Execution quality.
Withdrawals
None settled
No withdrawal request was settled in this month: 0, so there is no timing to report.
Read from the client portal’s database. Measured from the time a withdrawal was requested in the portal to the time it was settled there, which means approved by GIO4X and debited from the client’s wallet, for requests settled in the month (UTC), in clock hours including nights and weekends. The payment itself is made by hand afterwards and its time is not recorded, so it is not in these figures.
Incidents
Before records began
Incident records begin on . This month ended before that date, so there is nothing to report for it, and nothing is said about it.
Read from this website’s database: the incidents GIO4X staff have written and published whose recorded start falls in the month (UTC). A duration runs from the recorded start to the moment staff marked the incident resolved; an incident that ran into the next month is listed in the month it started. This is a list written by people. It is not produced by a monitor and is not a measurement of uptime. Each incident’s updates and post-mortem are on System status for 90 days.
Legal documents
The client portal’s database holds no published legal document, so it records no change to one in this month.
Read from the client portal’s database, which keeps one row for each legal document it serves (the terms a client accepts there), with a version number and the time of its latest change only. A document changed more than once is listed in the month of its latest change, and an earlier change is not on record. The legal pages of this website are files in the site’s source; their changes are not recorded in a database, so none can be listed here.
Counts
Counted by the client portal’s database. Accounts opened are trading accounts created in the month, demo and live apart; a demo account holds virtual funds. Tickets opened are support tickets created in the portal in the month; tickets resolved are those marked resolved in it, whenever they were opened. A count from 1 to 4 is not published, so that no single client or request can be read out of it; the floor is applied in the database before the figure leaves it.