biztrac. BETA
COMPANY REGISTER PROFILE
925903450 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
In liquidation UPDATED 03.10.2026
⚠NORVENTION AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Other technical consultancy

NORVENTION AS

Org. no. 925903450 Limited company (AS) Nome Incorporated 2020 In liquidation
Ownership graph ↗
Operating profit NOK −13,000
Equity NOK 31,000
Incorporated 2020
Share capital NOK 220,000

Signals

3 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).
  • Nylig endring 2026-10-06 Under avvikling registrert 2026-10-06.

NORVENTION AS is registered as a limited company in Nome, Telemark with organisation number 925903450. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2020. Registered share capital is NOK 220,000, divided into 22000 shares. The company's stated purpose is: “Salg og videreutvikling av ideer og andre produkter/tjenester som naturlig hører til dette.”.

Former names: HHM AS

Key figures · 2025

Operating profit
NOK −13,000
▲ +98 %
Equity
NOK 31,000
▼ −29 %
Est. value
NOK 51,000

Financial health · 2025

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

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

Who owns NORVENTION AS?

NORVENTION AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about NORVENTION AS

Who owns NORVENTION AS?

AUTENCIA AS is the largest registered owner, with 24.5%.

Who is the general manager of NORVENTION AS?

Magnus Ingebretsen is registered as general manager of NORVENTION AS.

Where is NORVENTION AS based?

NORVENTION AS has its business address in Ulefoss.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.