biztrac. BETA
COMPANY REGISTER PROFILE
992109882 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

MUR I SØR UTVIKLING AS

Org. no. 992109882 Limited company (AS) Kristiansand Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK 2.9m
Equity NOK 6.7m
Incorporated 2007
Share capital NOK 840,000

MUR I SØR UTVIKLING AS is registered as a limited company in Kristiansand, Agder with organisation number 992109882. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2007. Registered share capital is NOK 840,000, divided into 840000 shares. The company's stated purpose is: “Kjøp, deltakelse, utvikling, investering og eierskap i andre selskaper, eiendommer og virksomheter, samt forvaltning av avkastning fra disse, og det som står i forbindelse med dette.”.

Former names: ØSTERVEIEN 8 AS

Key figures · 2025

Operating profit
NOK 2.9m
▲ +192 %
Equity
NOK 6.7m
▲ +526 %
Est. value
NOK 5.4m

Financial health · 2025

Liquidity
0.48
Not satisfactory
Current assets ÷ current liabilities
Profitability
12.5%
Good
Return on total assets
Solidity
18.6%
Good
Equity as a share of total capital

Who owns MUR I SØR UTVIKLING AS?

MUR I SØR UTVIKLING AS
· NOK 2.9m profit

MUR I SØR UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MUR I SØR UTVIKLING AS own?

MUR I SØR UTVIKLING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about MUR I SØR UTVIKLING AS

Who owns MUR I SØR UTVIKLING AS?

TOM ARNE AAMODT AS is the largest registered owner, with 100.0%.

Who is the general manager of MUR I SØR UTVIKLING AS?

Tom Arne Aamodt is registered as general manager of MUR I SØR UTVIKLING AS.

Where is MUR I SØR UTVIKLING AS based?

MUR I SØR UTVIKLING AS has its business address in Søgne.

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.