BIZTRAC BETA
Other technical consultancy

LOGTEK AS

Org. no. 996257533 Limited company (AS) Stavanger Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 64.1m
Operating profit NOK 26.5m
Equity NOK 6.5m
Incorporated 2010
Employees 23
Share capital NOK 492,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LOGTEK AS is registered as a limited company in Stavanger, Rogaland with organisation number 996257533. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2010 and has 23 registered employees. Registered share capital is NOK 492,000, divided into 100 shares. The company's stated purpose is: “Petrofysisk prosessering.”. The most recent filed accounts, for the 2025 financial year, show NOK 64.1m in revenue and NOK 26.5m in operating profit.

Key figures · 2025

Revenue
NOK 64.1m
Operating profit
NOK 26.5m
Equity
NOK 6.5m
Est. value
NOK 83.7m

Financial health · 2025

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

Who owns LOGTEK AS?

LOGTEK CONSULTING AS
LOGTEK AS
NOK 64.1m rev. · NOK 26.5m profit

LOGTEK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LOGTEK AS own?

LOGTEK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LOGTEK AS

Who owns LOGTEK AS?

LOGTEK CONSULTING AS is the largest registered owner, with 100.0%.

What is the revenue of LOGTEK AS?

LOGTEK AS had revenue of NOK 64.1m in 2025.

Who is the general manager of LOGTEK AS?

Annette Larsen is registered as general manager of LOGTEK AS.

Where is LOGTEK AS based?

LOGTEK AS has its business address in Stavanger.

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.