BIZTRAC BETA
Construction of residential and non-residential buildings

OMLAND BYGG AS

Org. no. 991230602 Limited company (AS) Lyngdal Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 839,000
Operating profit NOK 158,000
Equity NOK 12,000
Incorporated 2007
Share capital NOK 100,000

OMLAND BYGG AS is registered as a limited company in Lyngdal, Agder with organisation number 991230602. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Bygge- og anleggsvirksomhet, oppføre, eie, leie ut, samt selge bolig- og forretningseiendommer, utføre vaktmestertjenester, samt delta i selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 839,000 in revenue and NOK 158,000 in operating profit.

Key figures · 2024

Revenue
NOK 839,000
Operating profit
NOK 158,000
Equity
NOK 12,000
Est. value
NOK 448,000

Financial health · 2024

Liquidity
0.47
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns OMLAND BYGG AS?

HENRY OMLAND
OMLAND BYGG AS
NOK 839,000 rev. · NOK 158,000 profit

OMLAND BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OMLAND BYGG AS

Who owns OMLAND BYGG AS?

HENRY OMLAND is the largest registered owner, with 100.0%.

What is the revenue of OMLAND BYGG AS?

OMLAND BYGG AS had revenue of NOK 839,000 in 2024.

Who is the general manager of OMLAND BYGG AS?

Henry Omland is registered as general manager of OMLAND BYGG AS.

Where is OMLAND BYGG AS based?

OMLAND BYGG AS has its business address in Lyngdal.

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.