BIZTRAC BETA
Computer consultancy and computer facilities management activities

LAVOLL AS

Org. no. 925127515 Limited company (AS) Sør-Varanger Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 222,000
Operating profit NOK 7,000
Equity NOK 143,000
Incorporated 2020
Share capital NOK 30,000

LAVOLL AS is registered as a limited company in Sør-Varanger, Finnmark with organisation number 925127515. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Konsulent- og datatjenester. Investere i aksjer og andeler samt kjøp, salg og utleie av fast eiendom og alt som dermed står i forbindelse, samt deltakelse i tilsvarende selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 222,000 in revenue and NOK 7,000 in operating profit.

Key figures · 2025

Revenue
NOK 222,000
Operating profit
NOK 7,000
Equity
NOK 143,000
Est. value
NOK 129,000

Financial health · 2025

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

Who owns LAVOLL AS?

LAVOLL HOLDING AS
LAVOLL AS
NOK 222,000 rev. · NOK 7,000 profit

LAVOLL AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LAVOLL AS er morselskap for 3 datterselskaper:

Frequently asked questions about LAVOLL AS

Who owns LAVOLL AS?

LAVOLL HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LAVOLL AS?

LAVOLL AS had revenue of NOK 222,000 in 2025.

Who is the general manager of LAVOLL AS?

Freddy Karlsen Lavoll is registered as general manager of LAVOLL AS.

Where is LAVOLL AS based?

LAVOLL AS has its business address in Bugøynes.

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.