BIZTRAC BETA
Other technical consultancy

DRIV INVEST AS

Org. no. 998264340 Limited company (AS) Asker Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −15,000
Equity NOK 6.3m
Incorporated 2012
Share capital NOK 30,000

Signals

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

DRIV INVEST AS is registered as a limited company in Asker, Akershus with organisation number 998264340. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investeringer i aksjer og eiendom og alt som naturlig hører herunder, samt rådgivningsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK 6.3m
Est. value
NOK 5.9m

Financial health · 2025

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

Who owns DRIV INVEST AS?

TROND INGAR IVERSEN
DRIV INVEST AS
NOK 0 rev. · NOK −15,000 profit

DRIV INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DRIV INVEST AS own?

DRIV INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about DRIV INVEST AS

Who owns DRIV INVEST AS?

TROND INGAR IVERSEN is the largest registered owner, with 100.0%.

What is the revenue of DRIV INVEST AS?

DRIV INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of DRIV INVEST AS?

Trond Ingar Iversen is registered as general manager of DRIV INVEST AS.

Where is DRIV INVEST AS based?

DRIV INVEST AS has its business address in Vollen.

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.