BIZTRAC BETA
Electrical installation

TINE II INVEST AS

Org. no. 922356106 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −215,000
Equity NOK 4.8m
Incorporated 2019
Share capital NOK 54,000

Signals

3 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−215k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-06-23 Adresseendring registrert 2026-06-23.

TINE II INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 922356106. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2019. Registered share capital is NOK 54,000, divided into 60 shares. The company's stated purpose is: “Investering i aksjer, eiendom, løsøre og hva dermed står i forbindelse, direkte eller via deltakelse i andre virksomheter.”.

Key figures · 2024

Operating profit
NOK −215,000
Equity
NOK 4.8m
Est. value
NOK 18.6m

Financial health · 2024

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

Who owns TINE II INVEST AS?

TORE AKSEL SÆTHER
TINE II INVEST AS
· NOK −215,000 profit

TINE II INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TINE II INVEST AS own?

TINE II INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TINE II INVEST AS

Who owns TINE II INVEST AS?

TORE AKSEL SÆTHER is the largest registered owner, with 96.7%.

Who is the general manager of TINE II INVEST AS?

Christine Sæther is registered as general manager of TINE II INVEST AS.

Where is TINE II INVEST AS based?

TINE II INVEST 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.