BIZTRAC BETA
Rental and operating of own or leased real estate

BJØRN WIRKOLASVEI 11 AS

Org. no. 997712994 Limited company (AS) Hammerfest Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 5.8m
Operating profit NOK 7.9m
Equity NOK 8.4m
Incorporated 2011
Share capital NOK 581,000

Signals

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

BJØRN WIRKOLASVEI 11 AS is registered as a limited company in Hammerfest, Finnmark with organisation number 997712994. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 581,000, divided into 100000 shares. The company's stated purpose is: “Forvaltning og drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.8m in revenue and NOK 7.9m in operating profit.

Key figures · 2025

Revenue
NOK 5.8m
Operating profit
NOK 7.9m
Equity
NOK 8.4m
Est. value
NOK 20.9m

Financial health · 2025

Liquidity
1.61
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
40.6%
Very good
Equity as a share of total capital

Who owns BJØRN WIRKOLASVEI 11 AS?

BOREAL NORGE AS
BJØRN WIRKOLASVEI 11 AS
NOK 5.8m rev. · NOK 7.9m profit

BJØRN WIRKOLASVEI 11 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BJØRN WIRKOLASVEI 11 AS er morselskap for 19 datterselskaper:

Frequently asked questions about BJØRN WIRKOLASVEI 11 AS

Who owns BJØRN WIRKOLASVEI 11 AS?

BOREAL NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of BJØRN WIRKOLASVEI 11 AS?

BJØRN WIRKOLASVEI 11 AS had revenue of NOK 5.8m in 2025.

Where is BJØRN WIRKOLASVEI 11 AS based?

BJØRN WIRKOLASVEI 11 AS has its business address in Hammerfest.

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.