biztrac. BETA
COMPANY REGISTER PROFILE
831892072 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

OPPETVEITEN TOMT AS

Org. no. 831892072 Limited company (AS) Haugesund Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 32,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

OPPETVEITEN TOMT AS is registered as a limited company in Haugesund, Rogaland with organisation number 831892072. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tomteutvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
▼ −3 %
Equity
NOK 32,000
▼ −17 %
Est. value
NOK 29,000

Financial health · 2025

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

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

Who owns OPPETVEITEN TOMT AS?

OPPETVEITEN TOMT AS
NOK 0 rev. · NOK −9,000 profit

OPPETVEITEN TOMT AS has 1 registered shareholder:

All shareholders and roles →

Group structure

OPPETVEITEN TOMT AS er morselskap for 210 datterselskaper:

Frequently asked questions about OPPETVEITEN TOMT AS

Who owns OPPETVEITEN TOMT AS?

SFR HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of OPPETVEITEN TOMT AS?

OPPETVEITEN TOMT AS had revenue of NOK 0 in 2025.

Where is OPPETVEITEN TOMT AS based?

OPPETVEITEN TOMT AS has its business address in Haugesund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.