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

ORHUSVEIEN 75-77 AS

Org. no. 925009288 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 24.6m
Operating profit NOK 12.1m
Equity NOK 213.8m
Incorporated 2020
Share capital NOK 30,000

ORHUSVEIEN 75-77 AS is registered as a limited company in Oslo, Oslo with organisation number 925009288. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å eie og/eller drive fast eiendom og investere i andre selskaper, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 24.6m in revenue and NOK 12.1m in operating profit.

Former names: HKBN 3-1 AS, BULK HANEKLEIVA AS

Key figures · 2025

Revenue
NOK 24.6m
▲ +137 %
Operating profit
NOK 12.1m
▲ +121 %
Equity
NOK 213.8m
▼ −5 %
Est. value
NOK 182.8m

Financial health · 2025

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

Who owns ORHUSVEIEN 75-77 AS?

ORHUSVEIEN 75-77 AS
NOK 24.6m rev. · NOK 12.1m profit

ORHUSVEIEN 75-77 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ORHUSVEIEN 75-77 AS er morselskap for 42 datterselskaper:

Frequently asked questions about ORHUSVEIEN 75-77 AS

Who owns ORHUSVEIEN 75-77 AS?

PEF HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ORHUSVEIEN 75-77 AS?

ORHUSVEIEN 75-77 AS had revenue of NOK 24.6m in 2025.

Where is ORHUSVEIEN 75-77 AS based?

ORHUSVEIEN 75-77 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.