BIZTRAC BETA
Other technical consultancy

ØKSNES TEKNIKK AS

Org. no. 930854654 Limited company (AS) Moss Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 18.7m
Operating profit NOK 3.6m
Equity NOK 2.0m
Incorporated 2023
Share capital NOK 2.0m

Signals

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

ØKSNES TEKNIKK AS is registered as a limited company in Moss, Østfold with organisation number 930854654. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2023. Registered share capital is NOK 2.0m, divided into 30 shares. The company's stated purpose is: “Teknisk rådgivning, salg av maskiner og andre teknisk relaterte tjenester. Investeringer, og det som naturlig hører med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.7m in revenue and NOK 3.6m in operating profit.

Key figures · 2024

Revenue
NOK 18.7m
Operating profit
NOK 3.6m
Equity
NOK 2.0m
Est. value
NOK 16.5m

Financial health · 2024

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

Who owns ØKSNES TEKNIKK AS?

SATEMA AS
ØKSNES TEKNIKK AS
NOK 18.7m rev. · NOK 3.6m profit

ØKSNES TEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØKSNES TEKNIKK AS

Who owns ØKSNES TEKNIKK AS?

SATEMA AS is the largest registered owner, with 100.0%.

What is the revenue of ØKSNES TEKNIKK AS?

ØKSNES TEKNIKK AS had revenue of NOK 18.7m in 2024.

Who is the general manager of ØKSNES TEKNIKK AS?

Kjell Roger Silden Øksnes is registered as general manager of ØKSNES TEKNIKK AS.

Where is ØKSNES TEKNIKK AS based?

ØKSNES TEKNIKK AS has its business address in Moss.

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.