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

LUDVIGSEN BYGG AS

Org. no. 922188092 Limited company (AS) Øygarden Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 11.3m
Operating profit NOK 734,000
Equity NOK 687,000
Incorporated 2018
Employees 11
Share capital NOK 30,000

LUDVIGSEN BYGG AS is registered as a limited company in Øygarden, Vestland with organisation number 922188092. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Anleggsvirksomhet og byggvirksomhet og omsetning av bygg og alt hva som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.3m in revenue and NOK 734,000 in operating profit.

Key figures · 2025

Revenue
NOK 11.3m
▲ +62 %
Operating profit
NOK 734,000
▲ +284 %
Equity
NOK 687,000
▲ +328 %
Est. value
NOK 2.4m

Financial health · 2025

Liquidity
1.43
Satisfactory
Current assets ÷ current liabilities
Profitability
21.6%
Very good
Return on total assets
Solidity
13.8%
Satisfactory
Equity as a share of total capital

Who owns LUDVIGSEN BYGG AS?

LUDVIGSEN BYGG AS
NOK 11.3m rev. · NOK 734,000 profit

LUDVIGSEN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUDVIGSEN BYGG AS

Who owns LUDVIGSEN BYGG AS?

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

What is the revenue of LUDVIGSEN BYGG AS?

LUDVIGSEN BYGG AS had revenue of NOK 11.3m in 2025.

Where is LUDVIGSEN BYGG AS based?

LUDVIGSEN BYGG AS has its business address in Straume.

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.