BIZTRAC BETA
Other captive investment companies

KURLAND OPPMÅLING AS

Org. no. 911810549 Limited company (AS) Rælingen Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 1.0m
Incorporated 2013
Share capital NOK 30,000

Signals

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

KURLAND OPPMÅLING AS is registered as a limited company in Rælingen, Akershus with organisation number 911810549. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, samt virksomhet som står i naturlig sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 1.0m
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns KURLAND OPPMÅLING AS?

STEFFEN ROCCO FLEISCHER
KURLAND OPPMÅLING AS
NOK 0 rev. · NOK −13,000 profit

KURLAND OPPMÅLING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KURLAND OPPMÅLING AS own?

KURLAND OPPMÅLING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KURLAND OPPMÅLING AS

Who owns KURLAND OPPMÅLING AS?

STEFFEN ROCCO FLEISCHER is the largest registered owner, with 100.0%.

What is the revenue of KURLAND OPPMÅLING AS?

KURLAND OPPMÅLING AS had revenue of NOK 0 in 2025.

Where is KURLAND OPPMÅLING AS based?

KURLAND OPPMÅLING AS has its business address in Fjerdingby.

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.