BIZTRAC BETA
Retail sale of information and communication equipment

LAVALO AS

Org. no. 932729261 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −2,000
Equity NOK 22,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LAVALO AS is registered as a limited company in Bergen, Vestland with organisation number 932729261. The business is classified under retail sale of information and communication equipment (NACE 47.400). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Netthandel. Salg av varer i Norge og Verden.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 22,000
Est. value
NOK 28,000

Financial health · 2024

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 LAVALO AS?

EGK INVEST AS
LAVALO AS
NOK 0 rev. · NOK −2,000 profit

LAVALO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAVALO AS

Who owns LAVALO AS?

EGK INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of LAVALO AS?

LAVALO AS had revenue of NOK 0 in 2024.

Who is the general manager of LAVALO AS?

Eirik Grothen Kristiansen is registered as general manager of LAVALO AS.

Where is LAVALO AS based?

LAVALO AS has its business address in Godvik.

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.