biztrac. BETA
COMPANY REGISTER PROFILE
927257629 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

BJØRKELANGEN NÆRINGSEIENDOM AS

Org. no. 927257629 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 414,000
Equity NOK 2.9m
Incorporated 2021
Share capital NOK 247,000

BJØRKELANGEN NÆRINGSEIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 927257629. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 247,000, divided into 1000 shares. The company's stated purpose is: “Utleie av egen fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 414,000 in operating profit.

Former names: NORDRE BLIKSRUD VEI 2 AS

Key figures · 2025

Revenue
NOK 2.3m
▲ +2 %
Operating profit
NOK 414,000
▼ −68 %
Equity
NOK 2.9m
▼ −14 %
Est. value
NOK 3.3m

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
2.0%
Weak
Return on total assets
Solidity
14.1%
Satisfactory
Equity as a share of total capital

Who owns BJØRKELANGEN NÆRINGSEIENDOM AS?

BJØRKELANGEN NÆRINGSEIENDOM AS
NOK 2.3m rev. · NOK 414,000 profit

BJØRKELANGEN NÆRINGSEIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJØRKELANGEN NÆRINGSEIENDOM AS

Who owns BJØRKELANGEN NÆRINGSEIENDOM AS?

LØVENSKIOLD EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BJØRKELANGEN NÆRINGSEIENDOM AS?

BJØRKELANGEN NÆRINGSEIENDOM AS had revenue of NOK 2.3m in 2025.

Where is BJØRKELANGEN NÆRINGSEIENDOM AS based?

BJØRKELANGEN NÆRINGSEIENDOM AS has its business address in Oslo.

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.