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

BYGGMESTER - LERVIK AS

Org. no. 930532932 Limited company (AS) Øygarden Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 119,000
Equity NOK 300,000
Incorporated 2022
Share capital NOK 30,000

BYGGMESTER - LERVIK AS is registered as a limited company in Øygarden, Vestland with organisation number 930532932. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tømrerarbeider.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 119,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
▲ +34 %
Operating profit
NOK 119,000
▲ +91 %
Equity
NOK 300,000
▲ +44 %
Est. value
NOK 535,000

Financial health · 2025

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
16.7%
Very good
Return on total assets
Solidity
41.1%
Very good
Equity as a share of total capital

Who owns BYGGMESTER - LERVIK AS?

BYGGMESTER - LERVIK AS
NOK 2.4m rev. · NOK 119,000 profit

BYGGMESTER - LERVIK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGGMESTER - LERVIK AS

Who owns BYGGMESTER - LERVIK AS?

Jørgen Lervik is the largest registered owner, with 100.0%.

What is the revenue of BYGGMESTER - LERVIK AS?

BYGGMESTER - LERVIK AS had revenue of NOK 2.4m in 2025.

Who is the general manager of BYGGMESTER - LERVIK AS?

Jørgen Lervik is registered as general manager of BYGGMESTER - LERVIK AS.

Where is BYGGMESTER - LERVIK AS based?

BYGGMESTER - LERVIK AS has its business address in Knarrevik.

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.