BIZTRAC BETA
Construction of residential and non-residential buildings

AANONSEN MARITIME BYGG AS

Org. no. 933498492 Limited company (AS) Arendal Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 179,000
Equity NOK 162,000
Incorporated 2024
Share capital NOK 30,000

AANONSEN MARITIME BYGG AS is registered as a limited company in Arendal, Agder with organisation number 933498492. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å drive med tømrerarbeid samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 179,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 179,000
Equity
NOK 162,000
Est. value
NOK 616,000

Financial health · 2024

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

Who owns AANONSEN MARITIME BYGG AS?

DAN-ROGER AANONSEN
AANONSEN MARITIME BYGG AS
NOK 1.7m rev. · NOK 179,000 profit

AANONSEN MARITIME BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AANONSEN MARITIME BYGG AS

Who owns AANONSEN MARITIME BYGG AS?

DAN-ROGER AANONSEN is the largest registered owner, with 100.0%.

What is the revenue of AANONSEN MARITIME BYGG AS?

AANONSEN MARITIME BYGG AS had revenue of NOK 1.7m in 2024.

Who is the general manager of AANONSEN MARITIME BYGG AS?

Dan-Roger Aanonsen is registered as general manager of AANONSEN MARITIME BYGG AS.

Where is AANONSEN MARITIME BYGG AS based?

AANONSEN MARITIME BYGG AS has its business address in Færvik.

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.