biztrac. BETA
COMPANY REGISTER PROFILE
918592423 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Landscape service activities

BLB LANDSKAP AS

Org. no. 918592423 Limited company (AS) Lillestrøm Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 12.5m
Operating profit NOK 968,000
Equity NOK 5.5m
Incorporated 2016
Employees 11
Share capital NOK 30,000

BLB LANDSKAP AS is registered as a limited company in Lillestrøm, Akershus with organisation number 918592423. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2016 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Beplantning av hager og parkanlegg, anleggsgartnervirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.5m in revenue and NOK 968,000 in operating profit.

Former names: BLB EIENDOM AS

Key figures · 2025

Revenue
NOK 12.5m
▲ +29 %
Operating profit
NOK 968,000
▼ −51 %
Equity
NOK 5.5m
▲ +8 %
Est. value
NOK 7.1m

Financial health · 2025

Liquidity
2.64
Very good
Current assets ÷ current liabilities
Profitability
9.4%
Satisfactory
Return on total assets
Solidity
41.0%
Very good
Equity as a share of total capital

Who owns BLB LANDSKAP AS?

BLB LANDSKAP AS
NOK 12.5m rev. · NOK 968,000 profit

BLB LANDSKAP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BLB LANDSKAP AS

Who owns BLB LANDSKAP AS?

Even Bjørnstad Lindblad is the largest registered owner, with 50.0%.

What is the revenue of BLB LANDSKAP AS?

BLB LANDSKAP AS had revenue of NOK 12.5m in 2025.

Who is the general manager of BLB LANDSKAP AS?

Even Bjørnstad Lindblad is registered as general manager of BLB LANDSKAP AS.

Where is BLB LANDSKAP AS based?

BLB LANDSKAP AS has its business address in Blaker.

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.