BIZTRAC BETA
Rental and operating of own or leased real estate

BØKELY AS

Org. no. 982511690 Limited company (AS) Sunnfjord Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 162,000
Operating profit NOK −558,000
Equity NOK −497,000
Incorporated 2000
Share capital NOK 1.0m

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−497k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−558k kr).

BØKELY AS is registered as a limited company in Sunnfjord, Vestland with organisation number 982511690. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2000. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg og drift av fast eiendom, herunder å ta del i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 162,000 in revenue and NOK −558,000 in operating profit.

Key figures · 2025

Revenue
NOK 162,000
Operating profit
NOK −558,000
Equity
NOK −497,000

Financial health · 2025

Liquidity
2.60
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-11.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BØKELY AS?

ARLE HJELMELAND AS
BØKELY AS
NOK 162,000 rev. · NOK −558,000 profit

BØKELY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BØKELY AS own?

BØKELY AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BØKELY AS

Who owns BØKELY AS?

ARLE HJELMELAND AS is the largest registered owner, with 100.0%.

What is the revenue of BØKELY AS?

BØKELY AS had revenue of NOK 162,000 in 2025.

Where is BØKELY AS based?

BØKELY AS has its business address in Førde.

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

Report a problem

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