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

LSABO AS

Org. no. 921822863 Limited company (AS) Asker Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −99,000
Equity NOK 16.3m
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−99k kr).

LSABO AS is registered as a limited company in Asker, Akershus with organisation number 921822863. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer i ett eller flere selskap, samt investeringer i offentlige noterte verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −99,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −99,000
▲ +0 %
Equity
NOK 16.3m
▼ −43 %
Est. value
NOK 20.1m

Financial health · 2025

Liquidity
698.53
Very good
Current assets ÷ current liabilities
Profitability
12.0%
Good
Return on total assets
Solidity
74.1%
Very good
Equity as a share of total capital

Who owns LSABO AS?

LSABO AS
NOK 0 rev. · NOK −99,000 profit

LSABO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LSABO AS own?

LSABO AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

LSABO AS er morselskap for 1 datterselskap:

Frequently asked questions about LSABO AS

Who owns LSABO AS?

Lars Sæbø is the largest registered owner, with 100.0%.

What is the revenue of LSABO AS?

LSABO AS had revenue of NOK 0 in 2025.

Where is LSABO AS based?

LSABO AS has its business address in Asker.

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.