BIZTRAC BETA
COMPANY REGISTER PROFILE
971248637 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Legal activities

ADVOKAT HARALD BJELKE WIBYE

Org. no. 971248637 Sole proprietorship (ENK) Fredrikstad Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 1.6m
Equity NOK 1.3m

ADVOKAT HARALD BJELKE WIBYE is registered as a sole proprietorship in Fredrikstad, Østfold with organisation number 971248637. The business is classified under legal activities (NACE 69.100). The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 1.6m in operating profit.

Former names: WIBYE HARALD BJELKE ADV

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 1.6m
Equity
NOK 1.3m
Est. value
NOK 6.0m

Financial health · 2025

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

Who owns ADVOKAT HARALD BJELKE WIBYE?

No shareholders are registered for ADVOKAT HARALD BJELKE WIBYE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ADVOKAT HARALD BJELKE WIBYE

What is the revenue of ADVOKAT HARALD BJELKE WIBYE?

ADVOKAT HARALD BJELKE WIBYE had revenue of NOK 2.2m in 2025.

Where is ADVOKAT HARALD BJELKE WIBYE based?

ADVOKAT HARALD BJELKE WIBYE has its business address in Fredrikstad.

Property

Business address Lykkeberg 2, 1606 Fredrikstad
Cadastral unit 3107-300/731/0/0
Building Kontor- og administrasjonsbygning, rådhus · 2 units

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