biztrac. BETA
COMPANY REGISTER PROFILE
924460245 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

LERVIK-BYGG AS

Org. no. 924460245 Limited company (AS) Stavanger Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 6.5m
Operating profit NOK −54,000
Equity NOK 138,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

LERVIK-BYGG AS is registered as a limited company in Stavanger, Rogaland with organisation number 924460245. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Snekker, tømrer, bygg og eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.5m in revenue and NOK −54,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.5m
▲ +35 %
Operating profit
NOK −54,000
▲ +79 %
Equity
NOK 138,000
▼ −37 %
Est. value
NOK 2.2m

Financial health · 2025

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
-3.4%
Not satisfactory
Return on total assets
Solidity
7.4%
Weak
Equity as a share of total capital

Who owns LERVIK-BYGG AS?

LERVIK-BYGG AS
NOK 6.5m rev. · NOK −54,000 profit

LERVIK-BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LERVIK-BYGG AS

Who owns LERVIK-BYGG AS?

TREVERKET AS is the largest registered owner, with 100.0%.

What is the revenue of LERVIK-BYGG AS?

LERVIK-BYGG AS had revenue of NOK 6.5m in 2025.

Where is LERVIK-BYGG AS based?

LERVIK-BYGG AS has its business address in Stavanger.

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.