BIZTRAC BETA
Rental and operating of own or leased real estate

TV4 INVEST AS

Org. no. 829345862 Limited company (AS) Drammen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 323,000
Operating profit NOK 137,000
Equity NOK 30,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TV4 INVEST AS is registered as a limited company in Drammen, Buskerud with organisation number 829345862. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i, eie, kjøpe, selge, utvikle, drifte og leie ut fast eiendom direkte eller gjennom underliggende selskaper, samt tilknyttet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 323,000 in revenue and NOK 137,000 in operating profit.

Key figures · 2025

Revenue
NOK 323,000
Operating profit
NOK 137,000
Equity
NOK 30,000
Est. value
NOK 256,000

Financial health · 2025

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

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

Who owns TV4 INVEST AS?

HELÉN INVEST AS
TV4 INVEST AS
NOK 323,000 rev. · NOK 137,000 profit

TV4 INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TV4 INVEST AS

Who owns TV4 INVEST AS?

HELÉN INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of TV4 INVEST AS?

TV4 INVEST AS had revenue of NOK 323,000 in 2025.

Where is TV4 INVEST AS based?

TV4 INVEST AS has its business address in Drammen.

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.