biztrac. BETA
COMPANY REGISTER PROFILE
984679955 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
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 −294,000
Equity NOK 30.3m
Incorporated 2002
Share capital NOK 1.4m

Signals

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

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.”.

Former names: NORDROP AS, POLLESTADVEGEN 231 AS

Key figures · 2025

Operating profit
NOK −294,000
▼ −202 %
Equity
NOK 30.3m
▲ +9 %
Est. value
NOK 30.0m

Financial health · 2025

Liquidity
0.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
5.0%
Weak
Return on total assets
Solidity
47.4%
Very good
Equity as a share of total capital

Who owns TEKO INVESTERING AS?

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 03.10.2026.

Report a problem

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