BIZTRAC BETA
Site preparation

LIVOLLEN MASKIN AS

Org. no. 926660586 Limited company (AS) Arendal Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK −963,000
Equity NOK 229,000
Incorporated 2021
Employees 5
Share capital NOK 100,000

Signals

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

LIVOLLEN MASKIN AS is registered as a limited company in Arendal, Agder with organisation number 926660586. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2021 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet i bygg og anlegg og hva som dermed står i forbindelse samt deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK −963,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK −963,000
Equity
NOK 229,000
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns LIVOLLEN MASKIN AS?

TORFINN LIVOLLEN
LIVOLLEN MASKIN AS
NOK 4.0m rev. · NOK −963,000 profit

LIVOLLEN MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIVOLLEN MASKIN AS

Who owns LIVOLLEN MASKIN AS?

TORFINN LIVOLLEN is the largest registered owner, with 100.0%.

What is the revenue of LIVOLLEN MASKIN AS?

LIVOLLEN MASKIN AS had revenue of NOK 4.0m in 2025.

Who is the general manager of LIVOLLEN MASKIN AS?

Torfinn Livollen is registered as general manager of LIVOLLEN MASKIN AS.

Where is LIVOLLEN MASKIN AS based?

LIVOLLEN MASKIN AS has its business address in Rykene.

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.