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

BERNHARD WEDDING AS

Org. no. 917292868 Limited company (AS) Hadsel Incorporated 1984 Active
Operating profit NOK −178,000
Equity NOK 26.6m
Incorporated 1984
Share capital NOK 665,000

Signals

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

BERNHARD WEDDING AS is registered as a limited company in Hadsel, Nordland with organisation number 917292868. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1984. Registered share capital is NOK 665,000, divided into 5362 shares. The company's stated purpose is: “Å eie og forvalte aksjer, utvikling og realisering av nye forretningsideer, forretningsførervirksomhet og nye forretningsideer, forretningsførervirksomhet og administrering av andre foretak.”.

Key figures · 2025

Operating profit
NOK −178,000
▼ −23 %
Equity
NOK 26.6m
▲ +0 %
Est. value
NOK 18.4m

Financial health · 2025

Liquidity
1.33
Satisfactory
Current assets ÷ current liabilities
Profitability
0.3%
Not satisfactory
Return on total assets
Solidity
72.8%
Very good
Equity as a share of total capital

Who owns BERNHARD WEDDING AS?

BERNHARD WEDDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does BERNHARD WEDDING AS own?

BERNHARD WEDDING AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about BERNHARD WEDDING AS

Who owns BERNHARD WEDDING AS?

ROAR WEDDING AS is the largest registered owner, with 52.7%.

Who is the general manager of BERNHARD WEDDING AS?

Roar Martin Wedding is registered as general manager of BERNHARD WEDDING AS.

Where is BERNHARD WEDDING AS based?

BERNHARD WEDDING AS has its business address in Stokmarknes.

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.