BIZTRAC BETA
Rental and operating of own or leased real estate

MOSEIDMOEN BOLIG AS

Org. no. 920126871 Limited company (AS) Vennesla Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK 533,000
Equity NOK 2.1m
Incorporated 2017
Share capital NOK 500,000

MOSEIDMOEN BOLIG AS is registered as a limited company in Vennesla, Agder with organisation number 920126871. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 500,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er eiendomsutvikling, kjøp og salg av eiendom, utleie av eiendom, investering i aksjer og verdipapirer, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK 533,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK 533,000
Equity
NOK 2.1m
Est. value
NOK 2.8m

Financial health · 2024

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

Who owns MOSEIDMOEN BOLIG AS?

SVENDSENGRUPPEN AS
MOSEIDMOEN BOLIG AS
NOK 1.0m rev. · NOK 533,000 profit

MOSEIDMOEN BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MOSEIDMOEN BOLIG AS

Who owns MOSEIDMOEN BOLIG AS?

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

What is the revenue of MOSEIDMOEN BOLIG AS?

MOSEIDMOEN BOLIG AS had revenue of NOK 1.0m in 2024.

Who is the general manager of MOSEIDMOEN BOLIG AS?

Jarl Ove Svendsen is registered as general manager of MOSEIDMOEN BOLIG AS.

Where is MOSEIDMOEN BOLIG AS based?

MOSEIDMOEN BOLIG AS has its business address in Vennesla.

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.