BIZTRAC BETA
Business and other management consultancy activities

DRIV RÅDGIVING AS

Org. no. 998228751 Limited company (AS) Nærøysund Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 146,000
Equity NOK 264,000
Incorporated 2012
Share capital NOK 30,000

DRIV RÅDGIVING AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 998228751. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie av personell med spisskompetanse, konsulenttjenester, prosjektledelse og alt som hermed står i forbindelse, herunder deltagelse i virksomhet i samarbeid med eller gjennom eierforhold i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 146,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 146,000
Equity
NOK 264,000
Est. value
NOK 890,000

Financial health · 2024

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

Who owns DRIV RÅDGIVING AS?

MARIT MÅØY HOLM
DRIV RÅDGIVING AS
NOK 1.5m rev. · NOK 146,000 profit

DRIV RÅDGIVING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about DRIV RÅDGIVING AS

Who owns DRIV RÅDGIVING AS?

MARIT MÅØY HOLM is the largest registered owner, with 33.3%.

What is the revenue of DRIV RÅDGIVING AS?

DRIV RÅDGIVING AS had revenue of NOK 1.5m in 2024.

Who is the general manager of DRIV RÅDGIVING AS?

Line Holm is registered as general manager of DRIV RÅDGIVING AS.

Where is DRIV RÅDGIVING AS based?

DRIV RÅDGIVING AS has its business address in Kolvereid.

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.