BIZTRAC BETA
Other education activities

MOMENTUM RÅDGIVNING AS

Org. no. 917803404 Limited company (AS) Karmøy Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 320,000
Operating profit NOK 270,000
Equity NOK 214,000
Incorporated 2016
Share capital NOK 330,000

MOMENTUM RÅDGIVNING AS is registered as a limited company in Karmøy, Rogaland with organisation number 917803404. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2016. Registered share capital is NOK 330,000, divided into 300 shares. The company's stated purpose is: “Utøve undervisning og konsulenttjenester innenfor bemanning og markedsføring samt det som naturlig står i forbindelse med dette, herunder å delta i andre selskaper med tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 320,000 in revenue and NOK 270,000 in operating profit.

Key figures · 2024

Revenue
NOK 320,000
Operating profit
NOK 270,000
Equity
NOK 214,000
Est. value
NOK 827,000

Financial health · 2024

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

Who owns MOMENTUM RÅDGIVNING AS?

KJETIL URHEIM
MOMENTUM RÅDGIVNING AS
NOK 320,000 rev. · NOK 270,000 profit

MOMENTUM RÅDGIVNING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MOMENTUM RÅDGIVNING AS

Who owns MOMENTUM RÅDGIVNING AS?

KJETIL URHEIM is the largest registered owner, with 70.0%.

What is the revenue of MOMENTUM RÅDGIVNING AS?

MOMENTUM RÅDGIVNING AS had revenue of NOK 320,000 in 2024.

Who is the general manager of MOMENTUM RÅDGIVNING AS?

Kjetil Urheim is registered as general manager of MOMENTUM RÅDGIVNING AS.

Where is MOMENTUM RÅDGIVNING AS based?

MOMENTUM RÅDGIVNING AS has its business address in Røyksund.

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.