BIZTRAC BETA
COMPANY REGISTER PROFILE
989266446 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

TOE AS

Org. no. 989266446 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −2,000
Equity NOK 3.8m
Incorporated 2005
Share capital NOK 201,000

Signals

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

TOE AS is registered as a limited company in Oslo, Oslo with organisation number 989266446. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 201,000, divided into 201 shares. The company's stated purpose is: “Selskapets virksomhet er investeringer i andre foretak og hva dermed er forbundet.”.

Key figures · 2025

Operating profit
NOK −2,000
▼ −6 %
Equity
NOK 3.8m
▼ −0 %
Est. value
NOK 3.5m

Financial health · 2025

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

Who owns TOE AS?

TOE AS
· NOK −2,000 profit

TOE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TOE AS own?

TOE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TOE AS

Who owns TOE AS?

IREN ELLEFSEN FAGERHØI is the largest registered owner, with 100.0%.

Where is TOE AS based?

TOE AS has its business address in Oslo.

Property

Business address Høgdaveien 1E, 0680 Oslo
Cadastral unit 301-149/598/0/0
Building Rekkehus · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.