BIZTRAC BETA
Preventive health care activities

OMTVEDT AS

Org. no. 928009807 Limited company (AS) Indre Østfold Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK −44,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

OMTVEDT AS is registered as a limited company in Indre Østfold, Østfold with organisation number 928009807. The business is classified under preventive health care activities (NACE 86.992). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK −44,000

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
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 OMTVEDT AS?

Linn Beate Omtvedt
OMTVEDT AS
NOK 0 rev. · NOK −4,000 profit

OMTVEDT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OMTVEDT AS own?

OMTVEDT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OMTVEDT AS

Who owns OMTVEDT AS?

Linn Beate Omtvedt is the largest registered owner, with 100.0%.

What is the revenue of OMTVEDT AS?

OMTVEDT AS had revenue of NOK 0 in 2025.

Who is the general manager of OMTVEDT AS?

Linn Beate Omtvedt is registered as general manager of OMTVEDT AS.

Where is OMTVEDT AS based?

OMTVEDT AS has its business address in Askim.

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.