BIZTRAC BETA
Rental and operating of own or leased real estate

OTORHINO AS

Org. no. 948189879 Limited company (AS) Drammen Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 1.1m
Equity NOK 17.2m
Incorporated 1986
Share capital NOK 155,000

OTORHINO AS is registered as a limited company in Drammen, Buskerud with organisation number 948189879. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1986. Registered share capital is NOK 155,000, divided into 1545 shares. The company's stated purpose is: “Drift av fast eiendom, investeringer og restrukturering av andre selskaper, rådgivningstjenester og forvaltning av verdipapirer og eiendom og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 1.1m
Equity
NOK 17.2m
Est. value
NOK 14.7m

Financial health · 2024

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

Who owns OTORHINO AS?

ERIK SPANDOW
OTORHINO AS
NOK 1.3m rev. · NOK 1.1m profit

OTORHINO AS has 2 registered shareholders:

All shareholders and roles →

Which companies does OTORHINO AS own?

OTORHINO AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about OTORHINO AS

Who owns OTORHINO AS?

ERIK SPANDOW is the largest registered owner, with 99.7%.

What is the revenue of OTORHINO AS?

OTORHINO AS had revenue of NOK 1.3m in 2024.

Who is the general manager of OTORHINO AS?

Torkel Knudsen is registered as general manager of OTORHINO AS.

Where is OTORHINO AS based?

OTORHINO AS has its business address in Drammen.

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.