Research Hub
Explore the article library
A focused FXMacroData research hub organized by market, release type, and workflow.
Search Results
Results for "NOK"
Showing 1-7 of 7
Norwegian Krone (NOK) Data Coverage: Indicators, Sources and Release Times
A practical guide to FXMacroData's 28 Norwegian krone series: who publishes them, when they are released in Oslo time and UTC, a real August 2026 CPI example from the API, and how EUR/NOK traders use the data.
Norges Bank Guide: Monetary Policy, Rate Path and NOK
How Norges Bank sets its policy rate and projected rate path, how flexible inflation targeting works, and which inflation, labour and yield signals matter for NOK.
NOK Press Release Brief: Norges Bank - Policy rate kept unchanged at 4%
Norges Bank’s Monetary and Financial Stability Committee decided to keep the policy rate unchanged at 4% at its meeting on 25 March. The...
NOK and Oil: The Commodity Currency FX Playbook
Norway earns roughly half its export revenues from oil and gas, making the NOK the G10’s most direct crude-price proxy. This analysis maps the EUR/NOK–Brent relationship, decodes Norges Bank’s reaction function, and provides a practical playbook for trading NOK across the commodity cycle.
Norway Government Bond Yields and Prices: NOK Guide
A country-specific guide to Norway government bond yields and prices, the NOK curve, monetary-policy and issuance drivers, FX transmission and the latest yields by maturity.
FXMacroData vs Statistics Norway (SSB) API: Norwegian CPI-ATE and GDP Data for NOK Traders
A buyer-guide comparison of Statistics Norway's free StatBank API (PxWebApi v2) and FXMacroData for NOK traders and developers who need Norwegian CPI, CPI-ATE, mainland GDP, and labour data in code.
Expanded Currency Coverage: NOK, SEK, PLN, DKK, KRW, BRL, and More
FXMacroData has expanded from 8 to 18 currencies, adding NOK, SEK, PLN, DKK, KRW, BRL, and more. Each new currency brings a deep indicator set — policy rates, inflation, trade data, bond yields, and labour market series — accessible through the same clean REST endpoint your pipeline already uses.
