biztrac. BETA
COMPANY REGISTER PROFILE
889240172 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

ANDERSEN & SØNN HOLDING AS

Org. no. 889240172 Limited company (AS) Askøy Incorporated 2005 Active
Operating profit NOK −78,000
Equity NOK 10.6m
Incorporated 2005
Share capital NOK 400,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−78k kr).

ANDERSEN & SØNN HOLDING AS is registered as a limited company in Askøy, Vestland with organisation number 889240172. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 400,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av verdipapirer samt kjøp, salg og utleie av fast eiendom.”.

Key figures · 2025

Operating profit
NOK −78,000
▼ −61 %
Equity
NOK 10.6m
▼ −13 %
Est. value
NOK 13.8m

Financial health · 2025

Liquidity
1.77
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
85.1%
Very good
Equity as a share of total capital

Who owns ANDERSEN & SØNN HOLDING AS?

ANDERSEN & SØNN HOLDING AS
· NOK −78,000 profit

ANDERSEN & SØNN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ANDERSEN & SØNN HOLDING AS own?

ANDERSEN & SØNN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ANDERSEN & SØNN HOLDING AS

Who owns ANDERSEN & SØNN HOLDING AS?

Trond Arild Andersen is the largest registered owner, with 100.0%.

Who is the general manager of ANDERSEN & SØNN HOLDING AS?

Trond Arild Andersen is registered as general manager of ANDERSEN & SØNN HOLDING AS.

Where is ANDERSEN & SØNN HOLDING AS based?

ANDERSEN & SØNN HOLDING AS has its business address in Kleppestø.

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.