BIZTRAC BETA
COMPANY REGISTER PROFILE
920884229 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

LBB EIENDOM AS

Org. no. 920884229 Limited company (AS) Hamar Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 65,000
Operating profit NOK −72,000
Equity NOK −4.0m
Incorporated 2018
Share capital NOK 1.0m

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−4,0 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−72k kr).

LBB EIENDOM AS is registered as a limited company in Hamar, Innlandet with organisation number 920884229. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 1.0m, divided into 100 shares. The company's stated purpose is: “Eiendomsutvikling og annet hva som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 65,000 in revenue and NOK −72,000 in operating profit.

Key figures · 2025

Revenue
NOK 65,000
Operating profit
NOK −72,000
▲ +19 %
Equity
NOK −4.0m
▼ −28 %

Financial health · 2025

Liquidity
580.59
Very good
Current assets ÷ current liabilities
Profitability
-0.6%
Not satisfactory
Return on total assets
Solidity
-34.4%
Weak
Equity as a share of total capital

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

Who owns LBB EIENDOM AS?

LBB EIENDOM AS
NOK 65,000 rev. · NOK −72,000 profit

LBB EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LBB EIENDOM AS

Who owns LBB EIENDOM AS?

ECOSØR HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of LBB EIENDOM AS?

LBB EIENDOM AS had revenue of NOK 65,000 in 2025.

Where is LBB EIENDOM AS based?

LBB EIENDOM AS has its business address in Hamar.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.