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

OLE PETTERSEN EIENDOMSSELSKAP AS

Org. no. 967355941 Limited company (AS) Trondheim Incorporated 1993 Active
Operating profit NOK −22,000
Equity NOK 243,000
Incorporated 1993
Share capital NOK 100,000

Signals

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

OLE PETTERSEN EIENDOMSSELSKAP AS is registered as a limited company in Trondheim, Trøndelag with organisation number 967355941. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1993. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie, drive og eventuelt selge eiendommer, samt deltakelse som aksjonær eller på annen måte i andre foretagender.”.

Key figures · 2025

Operating profit
NOK −22,000
▲ +1 %
Equity
NOK 243,000
▲ +5 %
Est. value
NOK 221,000

Financial health · 2025

Liquidity
1.77
Good
Current assets ÷ current liabilities
Profitability
-1.9%
Not satisfactory
Return on total assets
Solidity
99.3%
Very good
Equity as a share of total capital

Who owns OLE PETTERSEN EIENDOMSSELSKAP AS?

OLE PETTERSEN EIENDOMSSELSKAP AS
· NOK −22,000 profit

OLE PETTERSEN EIENDOMSSELSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLE PETTERSEN EIENDOMSSELSKAP AS

Who owns OLE PETTERSEN EIENDOMSSELSKAP AS?

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

Who is the general manager of OLE PETTERSEN EIENDOMSSELSKAP AS?

Ole Edvard Pettersen is registered as general manager of OLE PETTERSEN EIENDOMSSELSKAP AS.

Where is OLE PETTERSEN EIENDOMSSELSKAP AS based?

OLE PETTERSEN EIENDOMSSELSKAP AS has its business address in Trondheim.

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.