BIZTRAC BETA
COMPANY REGISTER PROFILE
833779052 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

A. BARUSAS HOLDING AS

Org. no. 833779052 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK 11,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

A. BARUSAS HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 833779052. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie aksjer og andeler i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −12,000
Equity
NOK 11,000

Who owns A. BARUSAS HOLDING AS?

A. BARUSAS HOLDING AS
· NOK −12,000 profit

A. BARUSAS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does A. BARUSAS HOLDING AS own?

A. BARUSAS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about A. BARUSAS HOLDING AS

Who owns A. BARUSAS HOLDING AS?

AURIMAS BARUSAS is the largest registered owner, with 100.0%.

Where is A. BARUSAS HOLDING AS based?

A. BARUSAS HOLDING AS has its business address in Ytre Arna.

Property

Business address Gudrun Kolderups veg 2, 5265 Ytre Arna
Cadastral unit 4601-302/300/0/0
Building Annen bygning for overnatting · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.