BIZTRAC BETA
Buying and selling of own real estate

TELLUS-STOX AS

Org. no. 985890056 Limited company (AS) Oslo Incorporated 2003 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK −152,000
Incorporated 2003
Share capital NOK 100,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−152k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TELLUS-STOX AS is registered as a limited company in Oslo, Oslo with organisation number 985890056. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av aksjer samt handel med andre finansielle instrumenter og deltagelse i andre selskaper, herunder konsulentvirksomhet i disse sammenhenger.”.

Key figures · 2024

Operating profit
NOK −9,000
Equity
NOK −152,000

Financial health · 2024

Liquidity
86.35
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-29.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TELLUS-STOX AS?

STOR-OSLO HOLDING AS
TELLUS-STOX AS
· NOK −9,000 profit

TELLUS-STOX AS has 1 registered shareholder:

All shareholders and roles →

Group structure

TELLUS-STOX AS er morselskap for 2 datterselskaper:

Frequently asked questions about TELLUS-STOX AS

Who owns TELLUS-STOX AS?

STOR-OSLO HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of TELLUS-STOX AS?

Erik Furre is registered as general manager of TELLUS-STOX AS.

Where is TELLUS-STOX AS based?

TELLUS-STOX 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.