BIZTRAC BETA
Uoppgitt

MEDIUMTALL INVEST AS

Org. no. 823726872 Limited company (AS) Bærum Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 384,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

MEDIUMTALL INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 823726872. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 150 shares. The company's stated purpose is: “Investering og eierskap i selskaper.”. 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 384,000
Est. value
NOK 451,000

Financial health · 2025

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

Who owns MEDIUMTALL INVEST AS?

MARTIN STEFFENSEN
MEDIUMTALL INVEST AS
NOK 0 rev. · NOK −8,000 profit

MEDIUMTALL INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MEDIUMTALL INVEST AS own?

MEDIUMTALL INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MEDIUMTALL INVEST AS

Who owns MEDIUMTALL INVEST AS?

MARTIN STEFFENSEN is the largest registered owner, with 100.0%.

What is the revenue of MEDIUMTALL INVEST AS?

MEDIUMTALL INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of MEDIUMTALL INVEST AS?

Martin Steffensen is registered as general manager of MEDIUMTALL INVEST AS.

Where is MEDIUMTALL INVEST AS based?

MEDIUMTALL INVEST AS has its business address in Fornebu.

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.