biztrac. BETA
COMPANY REGISTER PROFILE
819790442 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

OLE NORDGÅRD AS

Org. no. 819790442 Limited company (AS) Tromsø Incorporated 2017 Active
Revenue 2025 NOK 0
Operating profit NOK −954,000
Equity NOK 13.7m
Incorporated 2017
Share capital NOK 285,000

Signals

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

OLE NORDGÅRD AS is registered as a limited company in Tromsø, Troms with organisation number 819790442. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2017. Registered share capital is NOK 285,000, divided into 30 shares. The company's stated purpose is: “Investering i aksjer og fast eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −954,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −954,000
▼ −60 %
Equity
NOK 13.7m
▼ −5 %
Est. value
NOK 12.5m

Financial health · 2025

Liquidity
-2.45
Not satisfactory
Current assets ÷ current liabilities
Profitability
-5.2%
Not satisfactory
Return on total assets
Solidity
102.4%
Very good
Equity as a share of total capital

Who owns OLE NORDGÅRD AS?

OLE NORDGÅRD AS
NOK 0 rev. · NOK −954,000 profit

OLE NORDGÅRD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLE NORDGÅRD AS

Who owns OLE NORDGÅRD AS?

Tine Nordgård is the largest registered owner, with 100.0%.

What is the revenue of OLE NORDGÅRD AS?

OLE NORDGÅRD AS had revenue of NOK 0 in 2025.

Who is the general manager of OLE NORDGÅRD AS?

Tine Nordgård is registered as general manager of OLE NORDGÅRD AS.

Where is OLE NORDGÅRD AS based?

OLE NORDGÅRD AS has its business address in Tromsø.

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.