BIZTRAC BETA
COMPANY REGISTER PROFILE
934890418 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Buying and selling of own real estate

ROMSDAL EIENDOMSSERVICE AS

Org. no. 934890418 Limited company (AS) Hustadvika Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 275,000
Operating profit NOK 15,000
Equity NOK 40,000
Incorporated 2025
Share capital NOK 30,000

ROMSDAL EIENDOMSSERVICE AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 934890418. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Oppføre eneboliger, samt annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 275,000 in revenue and NOK 15,000 in operating profit.

Key figures · 2025

Revenue
NOK 275,000
Operating profit
NOK 15,000
Equity
NOK 40,000
Est. value
NOK 65,000

Financial health · 2025

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

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

Who owns ROMSDAL EIENDOMSSERVICE AS?

SUSANNE GANGSØY SLETTEDAL
ROMSDAL EIENDOMSSERVICE AS
NOK 275,000 rev. · NOK 15,000 profit

ROMSDAL EIENDOMSSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROMSDAL EIENDOMSSERVICE AS

Who owns ROMSDAL EIENDOMSSERVICE AS?

SUSANNE GANGSØY SLETTEDAL is the largest registered owner, with 100.0%.

What is the revenue of ROMSDAL EIENDOMSSERVICE AS?

ROMSDAL EIENDOMSSERVICE AS had revenue of NOK 275,000 in 2025.

Where is ROMSDAL EIENDOMSSERVICE AS based?

ROMSDAL EIENDOMSSERVICE AS has its business address in Molde.

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.