BIZTRAC BETA
Business and other management consultancy activities

MOEMENTUM FORSIKRING AS

Org. no. 948659336 Limited company (AS) Oslo Incorporated 1988 Active
Ownership graph ↗
Operating profit NOK −78,000
Equity NOK 34,000
Incorporated 1988
Share capital NOK 150,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−78k kr).

MOEMENTUM FORSIKRING AS is registered as a limited company in Oslo, Oslo with organisation number 948659336. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1988. Registered share capital is NOK 150,000, divided into 1000 shares. The company's stated purpose is: “Selskapets formål er franchisesalg av forsikringer gjennom franchiseavtale med Tryg Forsikring A/S, CVR nr. 24260666, ved sin norske filial Tryg Forsikring, org. nr. 989 563 521, kjøp og salg av aksjer samt deltakelse i annen næringsvirksomhet.”.

Key figures · 2024

Operating profit
NOK −78,000
Equity
NOK 34,000
Est. value
NOK 56,000

Financial health · 2024

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

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

Who owns MOEMENTUM FORSIKRING AS?

MOEMENTUM HOLDING AS
MOEMENTUM FORSIKRING AS
· NOK −78,000 profit

MOEMENTUM FORSIKRING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MOEMENTUM FORSIKRING AS

Who owns MOEMENTUM FORSIKRING AS?

MOEMENTUM HOLDING AS is the largest registered owner, with 51.0%.

Who is the general manager of MOEMENTUM FORSIKRING AS?

Ole-Bengt Løgith Moe is registered as general manager of MOEMENTUM FORSIKRING AS.

Where is MOEMENTUM FORSIKRING AS based?

MOEMENTUM FORSIKRING AS has its business address in Oslo.

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.