BIZTRAC BETA
COMPANY REGISTER PROFILE
930116025 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 02.09.2026
⚠PEIRIS BRUDVIK AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Rental and operating of own or leased real estate

PEIRIS BRUDVIK AS

Org. no. 930116025 Limited company (AS) Bergen Incorporated 2022 In liquidation
Ownership graph ↗
Incorporated 2022
Share capital NOK 490,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

PEIRIS BRUDVIK AS is registered as a limited company in Bergen, Vestland with organisation number 930116025. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 490,000, divided into 490000 shares. The company's stated purpose is: “Eiendom, utleie, vedlikehold, helse, drift, legekontor.”.

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

Who owns PEIRIS BRUDVIK AS?

PEIRIS BRUDVIK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PEIRIS BRUDVIK AS

Who owns PEIRIS BRUDVIK AS?

KIM GEORG BRUDVIK is the largest registered owner, with 100.0%.

Where is PEIRIS BRUDVIK AS based?

PEIRIS BRUDVIK AS has its business address in Loddefjord.

Property

Business address Kjøkkelvikbrekkene 20, 5178 Loddefjord
Cadastral unit 4601-143/829/0/0
Building Annen kontorbygning · 2 units

10 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.