BIZTRAC BETA
Other captive investment companies

STEJERR INVEST AS

Org. no. 993067490 Limited company (AS) Trondheim Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK 12.6m
Incorporated 2008
Share capital NOK 1.4m

Signals

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

STEJERR INVEST AS is registered as a limited company in Trondheim, Trøndelag with organisation number 993067490. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2008. Registered share capital is NOK 1.4m, divided into 100 shares. The company's stated purpose is: “Investering i finansielle instrumenter/verdipapirer, herunder også lånefinansierte investeringer med verdipapirer og valuta, andre selskaper og eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 12.6m
Est. value
NOK 14.9m

Financial health · 2025

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

Who owns STEJERR INVEST AS?

TERJE EIDESMO
STEJERR INVEST AS
NOK 0 rev. · NOK −18,000 profit

STEJERR INVEST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does STEJERR INVEST AS own?

STEJERR INVEST AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about STEJERR INVEST AS

Who owns STEJERR INVEST AS?

TERJE EIDESMO is the largest registered owner, with 70.0%.

What is the revenue of STEJERR INVEST AS?

STEJERR INVEST AS had revenue of NOK 0 in 2025.

Where is STEJERR INVEST AS based?

STEJERR INVEST AS has its business address in Ranheim.

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.