BIZTRAC BETA
COMPANY REGISTER PROFILE
944687297 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

OHREN AS

Org. no. 944687297 Limited company (AS) Oslo Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 70,000
Operating profit NOK −41,000
Equity NOK 1.5m
Incorporated 1987
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−41k kr).

OHREN AS is registered as a limited company in Oslo, Oslo with organisation number 944687297. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1987. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering i, og drift og utvikling av fast eiendom, samt konsulentvirksomhet i forbindelse med IT-baserte forretningssystemer.”. The most recent filed accounts, for the 2025 financial year, show NOK 70,000 in revenue and NOK −41,000 in operating profit.

Former names: DR SALVESEN AS

Key figures · 2025

Revenue
NOK 70,000
Operating profit
NOK −41,000
Equity
NOK 1.5m
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns OHREN AS?

NILS GUNNAR OHREN
OHREN AS
NOK 70,000 rev. · NOK −41,000 profit

OHREN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OHREN AS

Who owns OHREN AS?

NILS GUNNAR OHREN is the largest registered owner, with 100.0%.

What is the revenue of OHREN AS?

OHREN AS had revenue of NOK 70,000 in 2025.

Who is the general manager of OHREN AS?

Nils Gunnar Ohren is registered as general manager of OHREN AS.

Where is OHREN AS based?

OHREN 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.