BIZTRAC BETA
Civil engineering activities

AGILITEK AS

Org. no. 834310252 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 14.6m
Operating profit NOK 966,000
Equity NOK 267,000
Incorporated 2024
Employees 8
Share capital NOK 30,000

AGILITEK AS is registered as a limited company in Oslo, Oslo with organisation number 834310252. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2024 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby rådgivende ingeniørtjenester, herunder, men ikke begrenset til, rådgivning, utvikling, design, prosjektering, evaluering, testing og kvalitetssikring av tekniske systemer i byggeprosjekter.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.6m in revenue and NOK 966,000 in operating profit.

Key figures · 2025

Revenue
NOK 14.6m
Operating profit
NOK 966,000
Equity
NOK 267,000
Est. value
NOK 4.4m

Financial health · 2025

Liquidity
1.42
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.7%
Weak
Equity as a share of total capital

Who owns AGILITEK AS?

STRUKSNES INVEST AS
AGILITEK AS
NOK 14.6m rev. · NOK 966,000 profit

AGILITEK AS has 4 registered shareholders:

All shareholders and roles →

Group structure

AGILITEK AS er morselskap for 1 datterselskap:

Frequently asked questions about AGILITEK AS

Who owns AGILITEK AS?

STRUKSNES INVEST AS is the largest registered owner, with 30.0%.

What is the revenue of AGILITEK AS?

AGILITEK AS had revenue of NOK 14.6m in 2025.

Who is the general manager of AGILITEK AS?

Anders Jacobsen Møllevik is registered as general manager of AGILITEK AS.

Where is AGILITEK AS based?

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