biztrac. BETA
COMPANY REGISTER PROFILE
980712672 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

ASTEKO AS

Org. no. 980712672 Limited company (AS) Gjøvik Incorporated 1999 Active
Revenue 2025 NOK 285,000
Operating profit NOK 97,000
Equity NOK 1.3m
Incorporated 1999
Share capital NOK 1.0m

ASTEKO AS is registered as a limited company in Gjøvik, Innlandet with organisation number 980712672. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Investeringer, herunder kjøp, salg og drift av faste eiendommer, delta som aksjeeier eller på annen måte i andre selskaper, drive konsulentvirksomhet innen reklame og markedsføring.”. The most recent filed accounts, for the 2025 financial year, show NOK 285,000 in revenue and NOK 97,000 in operating profit.

Former names: SAGVEGEN 7 AS

Key figures · 2025

Revenue
NOK 285,000
▲ +1 %
Operating profit
NOK 97,000
▲ +53 %
Equity
NOK 1.3m
▲ +8 %
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns ASTEKO AS?

ASTEKO AS
NOK 285,000 rev. · NOK 97,000 profit

ASTEKO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ASTEKO AS

Who owns ASTEKO AS?

Stein Erik Kompen is the largest registered owner, with 100.0%.

What is the revenue of ASTEKO AS?

ASTEKO AS had revenue of NOK 285,000 in 2025.

Who is the general manager of ASTEKO AS?

Stein Erik Kompen is registered as general manager of ASTEKO AS.

Where is ASTEKO AS based?

ASTEKO AS has its business address in Gjøvik.

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.