biztrac. BETA
COMPANY REGISTER PROFILE
918616241 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other specialised construction activities n.e.c.

MOVEIEN 9 AS

Org. no. 918616241 Limited company (AS) Drammen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 215,000
Operating profit NOK 135,000
Equity NOK 739,000
Incorporated 2017
Share capital NOK 100,000

MOVEIEN 9 AS is registered as a limited company in Drammen, Buskerud with organisation number 918616241. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie, utvikling og drift av fast eiendom, og alt som står i forbindelse med dette - herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 215,000 in revenue and NOK 135,000 in operating profit.

Key figures · 2025

Revenue
NOK 215,000
▲ +3 %
Operating profit
NOK 135,000
▲ +3 %
Equity
NOK 739,000
▲ +16 %
Est. value
NOK 772,000

Financial health · 2025

Liquidity
0.30
Not satisfactory
Current assets ÷ current liabilities
Profitability
12.1%
Good
Return on total assets
Solidity
64.8%
Very good
Equity as a share of total capital

Who owns MOVEIEN 9 AS?

MOVEIEN 9 AS
NOK 215,000 rev. · NOK 135,000 profit

MOVEIEN 9 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MOVEIEN 9 AS

Who owns MOVEIEN 9 AS?

BORGERSEN UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of MOVEIEN 9 AS?

MOVEIEN 9 AS had revenue of NOK 215,000 in 2025.

Who is the general manager of MOVEIEN 9 AS?

Odd Remy Borgersen is registered as general manager of MOVEIEN 9 AS.

Where is MOVEIEN 9 AS based?

MOVEIEN 9 AS has its business address in Solbergelva.

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.