BIZTRAC BETA
Rental and operating of own or leased real estate

OSLO HUS TERMINAL AS

Org. no. 922260532 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 1.7m
Equity NOK 18.2m
Incorporated 2018
Share capital NOK 30,000

Signals

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

OSLO HUS TERMINAL AS is registered as a limited company in Oslo, Oslo with organisation number 922260532. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, utleie og utvikling av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 1.7m
Equity
NOK 18.2m
Est. value
NOK 15.4m

Financial health · 2025

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

Who owns OSLO HUS TERMINAL AS?

OSLO HUS AS
OSLO HUS TERMINAL AS
NOK 2.0m rev. · NOK 1.7m profit

OSLO HUS TERMINAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO HUS TERMINAL AS

Who owns OSLO HUS TERMINAL AS?

OSLO HUS AS is the largest registered owner, with 100.0%.

What is the revenue of OSLO HUS TERMINAL AS?

OSLO HUS TERMINAL AS had revenue of NOK 2.0m in 2025.

Who is the general manager of OSLO HUS TERMINAL AS?

Satinder Vir Singh is registered as general manager of OSLO HUS TERMINAL AS.

Where is OSLO HUS TERMINAL AS based?

OSLO HUS TERMINAL 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.