BIZTRAC BETA
COMPANY REGISTER PROFILE
988965413 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

TVP-MEDIAINVEST AS

Org. no. 988965413 Limited company (AS) Bærum Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −60,000
Equity NOK −213,000
Incorporated 2005
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−213k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−60k kr).

TVP-MEDIAINVEST AS is registered as a limited company in Bærum, Akershus with organisation number 988965413. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Selskapets virksomhet er investering i eiendom og plassering av kapital samt deltagelse i andre virksomheter. ”.

Former names: TVP-INVEST AS

Key figures · 2025

Operating profit
NOK −60,000
Equity
NOK −213,000

Financial health · 2025

Liquidity
0.50
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-73.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TVP-MEDIAINVEST AS?

ERIK PETTER PETTERSEN
TVP-MEDIAINVEST AS
· NOK −60,000 profit

TVP-MEDIAINVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TVP-MEDIAINVEST AS

Who owns TVP-MEDIAINVEST AS?

ERIK PETTER PETTERSEN is the largest registered owner, with 65.5%.

Who is the general manager of TVP-MEDIAINVEST AS?

Erik Petter Pettersen is registered as general manager of TVP-MEDIAINVEST AS.

Where is TVP-MEDIAINVEST AS based?

TVP-MEDIAINVEST AS has its business address in Eiksmarka.

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.