biztrac. BETA
COMPANY REGISTER PROFILE
935180643 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
General cleaning of buildings

MØRESERVICE AS

Org. no. 935180643 Limited company (AS) Aure Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −1,000
Equity NOK 785,000
Incorporated 2025
Share capital NOK 700,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1k kr).

MØRESERVICE AS is registered as a limited company in Aure, Møre og Romsdal with organisation number 935180643. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2025. Registered share capital is NOK 700,000, divided into 700000 shares. The company's stated purpose is: “Investere i bygg og eiendommer og andre selskap, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −1,000
Equity
NOK 785,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns MØRESERVICE AS?

MØRESERVICE AS
NOK 0 rev. · NOK −1,000 profit

MØRESERVICE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MØRESERVICE AS own?

MØRESERVICE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MØRESERVICE AS

Who owns MØRESERVICE AS?

Christian Kessler is the largest registered owner, with 50.0%.

What is the revenue of MØRESERVICE AS?

MØRESERVICE AS had revenue of NOK 0 in 2025.

Where is MØRESERVICE AS based?

MØRESERVICE AS has its business address in Tustna.

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.