BIZTRAC BETA
Construction of residential and non-residential buildings

LBB EIGEDOM AS

Org. no. 915363377 Limited company (AS) Lærdal Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK 1.2m
Equity NOK 2.0m
Incorporated 2015
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LBB EIGEDOM AS is registered as a limited company in Lærdal, Vestland with organisation number 915363377. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2015. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Kjøpe, selge, eie og utvikle fast eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK 1.2m
Equity
NOK 2.0m
Est. value
NOK 3.0m

Financial health · 2024

Liquidity
2.03
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.8%
Satisfactory
Equity as a share of total capital

Who owns LBB EIGEDOM AS?

LOKREIM HOLDING AS
LBB EIGEDOM AS
NOK 3.0m rev. · NOK 1.2m profit

LBB EIGEDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LBB EIGEDOM AS

Who owns LBB EIGEDOM AS?

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

What is the revenue of LBB EIGEDOM AS?

LBB EIGEDOM AS had revenue of NOK 3.0m in 2024.

Who is the general manager of LBB EIGEDOM AS?

Terje Lokreim is registered as general manager of LBB EIGEDOM AS.

Where is LBB EIGEDOM AS based?

LBB EIGEDOM AS has its business address in Lærdal.

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.