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

BRYGGA NARVIK AS

Org. no. 933923665 Limited company (AS) Narvik Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −43,000
Equity NOK 1.3m
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−43k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BRYGGA NARVIK AS is registered as a limited company in Narvik, Nordland with organisation number 933923665. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utleie av fast eiendom- og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”.

Former names: PARK124 AS

Key figures · 2025

Operating profit
NOK −43,000
▼ −420 %
Equity
NOK 1.3m
▲ +1834 %
Est. value
NOK 5.4m

Financial health · 2025

Liquidity
0.69
Weak
Current assets ÷ current liabilities
Profitability
14.3%
Good
Return on total assets
Solidity
7.1%
Weak
Equity as a share of total capital

Who owns BRYGGA NARVIK AS?

BRYGGA NARVIK AS
· NOK −43,000 profit

BRYGGA NARVIK AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BRYGGA NARVIK AS own?

BRYGGA NARVIK AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BRYGGA NARVIK AS

Who owns BRYGGA NARVIK AS?

PARK PROPERTY AS is the largest registered owner, with 66.7%.

Where is BRYGGA NARVIK AS based?

BRYGGA NARVIK AS has its business address in Narvik.

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.