NinjaTrader 8 for Latvian traders: data, VPS and latency

Search in Latvian for how to set up NinjaTrader 8 with live CME data and you get nothing useful. A couple of forum threads, some translated marketing, and a lot of advice written for someone sitting in Texas with a 4 millisecond ping. Meanwhile a trader in Riga has real questions nobody has answered: which feed actually delivers every tick, whether a VPS in Chicago is worth the money from here, and what the physics of the Atlantic mean for a DOM ladder.

This is the version for Riga. It is mostly about data and latency, because those are the two things that separate a NinjaTrader setup that works from one that quietly lies to you.

The data is the product

NinjaTrader 8 is a shell. The charts, the ladder, the volume profile and every order flow indicator you will ever run are just ways of drawing whatever the feed gives them. Feed it a weak stream and every study on top inherits the weakness, silently. There is no error message for bad data. There is just a footprint chart that looks plausible and is wrong.

Three distinctions decide everything.

Snapshot versus tick by tick. Some feeds send you a picture of the market several times a second. Others send you every single trade as it prints, with its size and whether it hit the bid or lifted the offer. Candles look almost identical either way. A footprint chart does not, because it is built by counting individual prints. If you intend to read order flow, a snapshot feed is not a cheaper option, it is the wrong instrument. Interactive Brokers, which many Latvians already hold an account with for stocks, is a snapshot feed. The dedicated futures routes, Rithmic, CQG, Continuum and Tradovate, deliver the tick stream.

Level 1 versus depth. Level 1 is best bid, best ask and trades. Depth of market adds the resting orders behind the top of book, which is what fills in a DOM ladder. Trading from the ladder without depth is like driving with the windscreen painted over. Trading a daily chart with depth is paying for a window you never look through.

Non-professional versus professional. CME Group sets the market data fees and your broker or vendor bills them on, per exchange group, per month. The classification you sign changes the amount substantially. Non-professional generally means own money, no financial licence or registration, no business use of the data. Read the declaration properly instead of ticking the cheaper box, because a retroactive reclassification arrives as a single very memorable invoice.

How NinjaTrader stores and replays it

Here is what most guides skip. NT8 keeps its price history in a database on your own disk, under your Documents folder. That local store is what your charts load from, what your backtests run on and what gets rebuilt when something goes wrong. Treat it as part of the setup, not as a temporary file.

Things worth knowing before they bite you:

• Days to load is not free. Each chart has a setting for how much history to pull. Ask for months of tick data across six charts and you will wait, and the platform will hold all of it in memory. Load what the strategy needs, not the maximum.
• Tick Replay is the honest backtest. Normally an indicator is calculated once per completed bar. Tick Replay recalculates it trade by trade, exactly as it would have updated live. For anything order flow based, a result without Tick Replay is not a result. It also requires that you actually hold tick data for that period, which brings us to the next point.
• Ask how much tick history you get. Feeds differ enormously here. Some give you a handful of days of tick history on download, others give months. Before you commit, ask specifically for ES, MES, NQ and MNQ, because that is what you will be testing on.
• Market Replay is separate. NT8 can download recorded sessions and play them back at speed, which is the cheapest practice available to a Latvian trader who cannot sit at the desk at 16:30 every day. Download a week of replay data on a Saturday and you can rehearse the American open on a Sunday morning.
• Session templates set the day boundary. CME futures do not have a calendar day. The trading day rolls over at 17:00 Chicago time, which is 01:00 in Riga. Your session template decides where a daily bar starts, where a volume profile resets and what counts as the overnight range. Get it wrong and every level you draw is anchored to the wrong point.

Latency from Riga, in numbers you can check

The CME matching engine sits in a data centre in Aurora, Illinois. Riga is about 7,360 km away in a straight line. Light in optical fibre travels at roughly 200,000 km per second, which puts the absolute theoretical floor for a round trip at about 74 milliseconds. No cable is straight, so your packets route through Stockholm or Frankfurt, across the Atlantic, then across the United States. Adding 30 to 50 percent over the floor is ordinary. Triple digit round trips from Riga are normal and not a sign anything is broken.

Measure your own rather than believing any published figure. Open a command prompt during the session, not at 2 a.m., and run a sustained ping against your broker's gateway. Then watch two things:

• The average tells you the distance tax you are paying. You cannot negotiate with it.
• The variation tells you whether you can trade. A rock steady 115 ms is a better connection than one averaging 70 ms that jumps to 500 every time somebody in the flat starts a video call. Jitter is what makes a ladder feel slippery.

Be clear about what latency does and does not change. It does not make you late to a trend. A 100 ms delay is irrelevant to someone trading a 15 minute chart on the ES. It matters when you are working limit orders at the touch, when you are scalping a two tick range, or when you are trying to react to a number in the first seconds after a release. If your edge lives inside a one second window, you are competing on a dimension where geography beats you and no VPS fully fixes it.

Finally, separate the two paths in your head. The order round trip goes platform to broker to exchange and back. The screen round trip goes exchange to your eyes. They are the same when NinjaTrader runs on your desk in Riga. They stop being the same the moment you introduce a remote machine.

Where to put the VPS

A hosted Windows machine near Chicago puts NinjaTrader within a couple of milliseconds of the exchange. That is real, and it is also the part people misunderstand, because you still sit in Riga looking at that machine through remote desktop across the same Atlantic. The orders get faster. The picture does not.

So the honest decision tree looks like this.

If you do take a VPS, a Frankfurt machine is worth considering as a middle option. Riga to Frankfurt is about 1,270 km, so your remote desktop stays responsive, and the server side leg to Chicago is on a fat, well engineered route rather than your residential line. It is a compromise rather than a win on both counts, but for a trader who wants uptime more than microseconds it is often the practical choice.

Specification matters less than people assume, with one exception. NinjaTrader leans on single core speed rather than core count, so a VPS advertising eight slow vCPUs may perform worse than a smaller instance with fast ones. Ask about the CPU generation. Insist on NVMe storage, because the tick database is written to constantly. And take 8 GB of RAM as a floor, 16 if you run several charts with depth.

Whatever you choose, plan for the failure. Know how to phone the broker to flatten a position, keep a tested mobile hotspot, and keep a second device that can reach the account. Latvia's grid and fibre are good, but a building level outage during the American open does not care about that.

Check who you are dealing with

The broker side is the one place where being in the EU actually gives a Latvian trader a tool most retail traders elsewhere lack. Latvijas Banka took over financial market supervision and publishes a financial market participant register. Anyone offering you investment services in Latvia should be findable in it, or authorised elsewhere in the EU and passporting in.

The regulator also warns publicly about firms soliciting Latvian clients without the required licence or authorisation. Read it once. The pattern it describes, a slick platform, aggressive account managers, an entity you cannot locate in any register, is exactly what gets pushed at people searching for trading content in Latvian.

The Riga clock

Latvia is on EET in winter and EEST in summer, and Chicago shifts too, so the gap is eight hours for most of the year. The American cash open, and the regular session for the equity index futures, lands at 16:30 Riga time. The big monthly data releases at 07:30 Chicago come in at 15:30. The Globex week opens Sunday at 01:00 Monday morning your time, and the daily maintenance halt runs from 00:00 to 01:00.

Two windows each year break the pattern, because the EU and the United States change clocks on different dates. The US springs forward on the second Sunday of March and the EU on the last, leaving about three weeks when the gap is seven hours and everything American happens an hour earlier for you. The reverse mismatch runs for about a week at the end of October, when the EU has already fallen back and the US has not. During those weeks the cash open is at 15:30 Riga time. Put both windows in your calendar now, along with the CME holiday schedule, because half sessions around American holidays produce thin, ugly price action that is not worth trading.

What VID expects when you win

Your broker is abroad, so nothing is withheld and nothing appears prefilled. A Latvian tax resident declares worldwide income, and it does not matter whether the money ever reaches a Latvian bank.

The State Revenue Service explains the regime on its page on income tax on capital gains. Capital assets include shares, equities and other financial instruments, and the rate on capital gains is 25.5%. VID's personal income tax rates page, updated at the end of 2025, confirms the same 25.5% for income from capital, with 33% applying to annual income from a higher band and a transitional 20% rate running to 2027 for gains on assets acquired before the end of 2024.

The part that catches people out is the rhythm of the filing, which is quarterly rather than annual once you are active:

• If your total capital gains income in a quarter exceeds €1,000, you file a capital gains declaration by the 15th of the month following the quarter and pay by the 23rd.
• If it stays at or below €1,000 in the quarter, you can declare annually instead, by 15 January of the following year, paying by 23 January.

Everything goes through the Electronic Declaration System. A profitable quarter in a US futures account will comfortably clear €1,000, so assume you are on the quarterly cycle and diary the dates rather than discovering them in the following spring.

Keep your records in euro. Convert each realised result at the rate on the date it happened rather than applying one convenient year end rate to the whole account, download the annual statement from the broker every January, and keep the fill history. Reconstructing a year of dollar denominated trades two years later is the single most miserable job in this entire hobby.

One last thing that belongs here rather than in the technical sections: leveraged futures can lose you more than you deposited. Margin is a performance bond, not the size of the risk. A fast move against a position can close the account and leave a debit balance. No feed, no VPS and no indicator changes that, including ours. Size accordingly.

This article is general information about configuring a trading platform and an outline of how Latvian rules work. It is not tax, legal or investment advice. Rates, thresholds and deadlines change, and your own circumstances may put you in a different position, so check the current rules with VID and Latvijas Banka and talk to a qualified Latvian adviser before you act.

ninjatrader 8 latvia

Educational content, not investment advice. Trading futures involves substantial risk of loss and is not suitable for every investor. Any reference to Algomyth results is hypothetical, simulated over historical data, and shown in full on the performance page; past performance does not guarantee future results.