BIZTRAC BETA
Rental and operating of own or leased real estate

BKI PROF.BIRKELANDSVEI 26 AS

Org. no. 975778703 Limited company (AS) Oslo Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 7.9m
Operating profit NOK 3.8m
Equity NOK 1.8m
Incorporated 1995
Share capital NOK 1.8m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BKI PROF.BIRKELANDSVEI 26 AS is registered as a limited company in Oslo, Oslo with organisation number 975778703. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1995. Registered share capital is NOK 1.8m, divided into 1776 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.9m in revenue and NOK 3.8m in operating profit.

Key figures · 2024

Revenue
NOK 7.9m
Operating profit
NOK 3.8m
Equity
NOK 1.8m
Est. value
NOK 6.9m

Financial health · 2024

Liquidity
0.83
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.4%
Not satisfactory
Equity as a share of total capital

Who owns BKI PROF.BIRKELANDSVEI 26 AS?

WILOG AS
BKI PROF.BIRKELANDSVEI 26 AS
NOK 7.9m rev. · NOK 3.8m profit

BKI PROF.BIRKELANDSVEI 26 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BKI PROF.BIRKELANDSVEI 26 AS

Who owns BKI PROF.BIRKELANDSVEI 26 AS?

WILOG AS is the largest registered owner, with 100.0%.

What is the revenue of BKI PROF.BIRKELANDSVEI 26 AS?

BKI PROF.BIRKELANDSVEI 26 AS had revenue of NOK 7.9m in 2024.

Where is BKI PROF.BIRKELANDSVEI 26 AS based?

BKI PROF.BIRKELANDSVEI 26 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 15.06.2026.

Report a problem

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