BIZTRAC BETA
Rental and operating of own or leased real estate

TEKO INVESTERING AS

Org. no. 984679955 Limited company (AS) Klepp Incorporated 2002 Active
Ownership graph ↗
Operating profit NOK −97,000
Equity NOK 27.9m
Incorporated 2002
Share capital NOK 1.4m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−97k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TEKO INVESTERING AS is registered as a limited company in Klepp, Rogaland with organisation number 984679955. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 1.4m, divided into 140000 shares. The company's stated purpose is: “Investering i og forvaltning av aksjer, verdipapirer, eiendom og driftsløsøre samt deltakelse i andre selskaper av enhver art.”.

Key figures · 2024

Operating profit
NOK −97,000
Equity
NOK 27.9m
Est. value
NOK 25.4m

Financial health · 2024

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

Who owns TEKO INVESTERING AS?

RETOL INVEST AS
TEKO INVESTERING AS
· NOK −97,000 profit

TEKO INVESTERING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does TEKO INVESTERING AS own?

TEKO INVESTERING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TEKO INVESTERING AS

Who owns TEKO INVESTERING AS?

RETOL INVEST AS is the largest registered owner, with 37.2%.

Who is the general manager of TEKO INVESTERING AS?

Egil Fosse is registered as general manager of TEKO INVESTERING AS.

Where is TEKO INVESTERING AS based?

TEKO INVESTERING AS has its business address in Orre.

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.