BIZTRAC BETA
Rental and operating of own or leased real estate

ANTHON WALLESVEI 43B AS

Org. no. 990589887 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −22,000
Equity NOK 2.2m
Incorporated 2006
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−22k kr).

ANTHON WALLESVEI 43B AS is registered as a limited company in Oslo, Oslo with organisation number 990589887. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Direkte eller indirekte å anskaffe, prosjektere, utbygge, eie, drive, leie ut og selge fast eiendom, og alt som er beslektet eller står i forbindelse med slik virksomhet. Selskapet skal også kunne eie eller delta i andre selskaper eller næringsforetak.”.

Key figures · 2024

Operating profit
NOK −22,000
Equity
NOK 2.2m
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
99.2%
Very good
Equity as a share of total capital

Who owns ANTHON WALLESVEI 43B AS?

AVANTOR AS
ANTHON WALLESVEI 43B AS
· NOK −22,000 profit

ANTHON WALLESVEI 43B AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ANTHON WALLESVEI 43B AS er morselskap for 36 datterselskaper:

Frequently asked questions about ANTHON WALLESVEI 43B AS

Who owns ANTHON WALLESVEI 43B AS?

AVANTOR AS is the largest registered owner, with 100.0%.

Who is the general manager of ANTHON WALLESVEI 43B AS?

Roy Åge Frivoll is registered as general manager of ANTHON WALLESVEI 43B AS.

Where is ANTHON WALLESVEI 43B AS based?

ANTHON WALLESVEI 43B AS has its business address in Oslo.

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.