BIZTRAC BETA
Other captive investment companies

MEDERLINGER AS

Org. no. 915321305 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 5.0m
Incorporated 2015
Share capital NOK 30,000

Signals

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

MEDERLINGER AS is registered as a limited company in Oslo, Oslo with organisation number 915321305. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Forvaltning eierandeler, aksjer og interesser i andre firma.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 5.0m
Est. value
NOK 4.6m

Financial health · 2025

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

Who owns MEDERLINGER AS?

TORKEL STEFFEN MELLINGEN
MEDERLINGER AS
NOK 0 rev. · NOK −14,000 profit

MEDERLINGER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MEDERLINGER AS own?

MEDERLINGER AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MEDERLINGER AS

Who owns MEDERLINGER AS?

TORKEL STEFFEN MELLINGEN is the largest registered owner, with 100.0%.

What is the revenue of MEDERLINGER AS?

MEDERLINGER AS had revenue of NOK 0 in 2025.

Who is the general manager of MEDERLINGER AS?

Torkel Steffen Mellingen is registered as general manager of MEDERLINGER AS.

Where is MEDERLINGER AS based?

MEDERLINGER AS has its business address in Oslo.

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.