BIZTRAC BETA
Development of building projects

LASSVEBERGV. 8 - 10 AS

Org. no. 927020866 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 129,000
Operating profit NOK −9,000
Equity NOK 105,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).

LASSVEBERGV. 8 - 10 AS is registered as a limited company in Trondheim, Trøndelag with organisation number 927020866. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investere i og bygge ut fast eiendom med tanke på utleie og salg samt det som naturlig står i forbindelse med dette, herunder eie og forvalte aksjer i andre selskaper innen samme og tilknyttede bransjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 129,000 in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 129,000
Operating profit
NOK −9,000
Equity
NOK 105,000
Est. value
NOK 96,000

Financial health · 2024

Liquidity
2464.92
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.3%
Not satisfactory
Equity as a share of total capital

Who owns LASSVEBERGV. 8 - 10 AS?

KEH HOLDING AS
LASSVEBERGV. 8 - 10 AS
NOK 129,000 rev. · NOK −9,000 profit

LASSVEBERGV. 8 - 10 AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LASSVEBERGV. 8 - 10 AS

Who owns LASSVEBERGV. 8 - 10 AS?

KEH HOLDING AS is the largest registered owner, with 40.0%.

What is the revenue of LASSVEBERGV. 8 - 10 AS?

LASSVEBERGV. 8 - 10 AS had revenue of NOK 129,000 in 2024.

Where is LASSVEBERGV. 8 - 10 AS based?

LASSVEBERGV. 8 - 10 AS has its business address in Ranheim.

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.