BIZTRAC BETA
Other technical consultancy

OILROX AS

Org. no. 914156459 Limited company (AS) Nordre Follo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 1.2m
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).

OILROX AS is registered as a limited company in Nordre Follo, Akershus with organisation number 914156459. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulentvirksomhet innen petroleumsteknologi samt å eie fast eiendom, eiendomsutvikling og utleie av fast eiendom, eie aksjer i andre selskapet, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 1.2m
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns OILROX AS?

KARL LUDVIG HESKESTAD
OILROX AS
NOK 0 rev. · NOK −8,000 profit

OILROX AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OILROX AS

Who owns OILROX AS?

KARL LUDVIG HESKESTAD is the largest registered owner, with 60.0%.

What is the revenue of OILROX AS?

OILROX AS had revenue of NOK 0 in 2025.

Who is the general manager of OILROX AS?

Karl Ludvig Heskestad is registered as general manager of OILROX AS.

Where is OILROX AS based?

OILROX AS has its business address in Langhus.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.