BIZTRAC BETA
COMPANY REGISTER PROFILE
922859736 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other technical consultancy

MØRE TEKNISKE AS

Org. no. 922859736 Limited company (AS) Sykkylven Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK −624,000
Equity NOK −750,000
Incorporated 2019
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−750k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−624k kr).

MØRE TEKNISKE AS is registered as a limited company in Sykkylven, Møre og Romsdal with organisation number 922859736. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 300 shares. The company's stated purpose is: “Utbygging av teknisk infrastruktur for fritidsbolig felt.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK −624,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
▲ +12 %
Operating profit
NOK −624,000
▼ −234 %
Equity
NOK −750,000
▼ −308 %

Financial health · 2025

Liquidity
6.67
Very good
Current assets ÷ current liabilities
Profitability
-9.8%
Not satisfactory
Return on total assets
Solidity
-12.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MØRE TEKNISKE AS?

MØRE TEKNISKE AS
NOK 1.2m rev. · NOK −624,000 profit

MØRE TEKNISKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MØRE TEKNISKE AS

Who owns MØRE TEKNISKE AS?

DAGS MASKIN AS is the largest registered owner, with 100.0%.

What is the revenue of MØRE TEKNISKE AS?

MØRE TEKNISKE AS had revenue of NOK 1.2m in 2025.

Where is MØRE TEKNISKE AS based?

MØRE TEKNISKE AS has its business address in Sykkylven.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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