BIZTRAC BETA
Publishing of books

VIVEL INVEST AS

Org. no. 999231667 Limited company (AS) Lier Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 77,000
Operating profit NOK 38,000
Equity NOK 1.3m
Incorporated 2012
Share capital NOK 50,000

VIVEL INVEST AS is registered as a limited company in Lier, Buskerud with organisation number 999231667. The business is classified under publishing of books (NACE 58.110). The company was incorporated in 2012. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Investeringsselskap, herunder å investere i aksjer, obligasjoner, fast eiendom, andeler i selskap etter selskapsloven og annet som står i naturlig forbindelse med dette. Utvikling, kjøp og salg av produkter - herunder utarbeidelse og publisering av bøker.”. The most recent filed accounts, for the 2025 financial year, show NOK 77,000 in revenue and NOK 38,000 in operating profit.

Key figures · 2025

Revenue
NOK 77,000
Operating profit
NOK 38,000
Equity
NOK 1.3m
Est. value
NOK 794,000

Financial health · 2025

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

Who owns VIVEL INVEST AS?

HANNE-LENE NORUP DAHLGREN
VIVEL INVEST AS
NOK 77,000 rev. · NOK 38,000 profit

VIVEL INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VIVEL INVEST AS own?

VIVEL INVEST AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about VIVEL INVEST AS

Who owns VIVEL INVEST AS?

HANNE-LENE NORUP DAHLGREN is the largest registered owner, with 100.0%.

What is the revenue of VIVEL INVEST AS?

VIVEL INVEST AS had revenue of NOK 77,000 in 2025.

Where is VIVEL INVEST AS based?

VIVEL INVEST AS has its business address in Lier.

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.