BIZTRAC BETA
Site preparation

Mosby Anlegg AS

Org. no. 953850443 Limited company (AS) Lillesand Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 128,000
Equity NOK 30,000
Incorporated 1989
Share capital NOK 100,000

Mosby Anlegg AS is registered as a limited company in Lillesand, Agder with organisation number 953850443. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1989. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transport- og anleggsvirksomhet samt alt hva hermed står i forbindelse, herunder deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 128,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 128,000
Equity
NOK 30,000
Est. value
NOK 344,000

Financial health · 2024

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.4%
Weak
Equity as a share of total capital

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

Who owns Mosby Anlegg AS?

HARRY MOSBY
Mosby Anlegg AS
NOK 1.7m rev. · NOK 128,000 profit

Mosby Anlegg AS has 1 registered shareholder:

All shareholders and roles →

Which companies does Mosby Anlegg AS own?

Mosby Anlegg AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about Mosby Anlegg AS

Who owns Mosby Anlegg AS?

HARRY MOSBY is the largest registered owner, with 100.0%.

What is the revenue of Mosby Anlegg AS?

Mosby Anlegg AS had revenue of NOK 1.7m in 2024.

Who is the general manager of Mosby Anlegg AS?

Kåre Trygve Mosby is registered as general manager of Mosby Anlegg AS.

Where is Mosby Anlegg AS based?

Mosby Anlegg AS has its business address in Lillesand.

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.