BIZTRAC BETA
Wholesale of solid, liquid and gaseous fuels and related products

BÅLY BUNKRING AS

Org. no. 992282932 Limited company (AS) Lindesnes Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 6.5m
Operating profit NOK 193,000
Equity NOK 1.4m
Incorporated 2007
Share capital NOK 500,000

BÅLY BUNKRING AS is registered as a limited company in Lindesnes, Agder with organisation number 992282932. The business is classified under wholesale of solid, liquid and gaseous fuels and related products (NACE 46.810). The company was incorporated in 2007. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Drive bunkringstasjon, samt hva hermed står i forbindelse, herunder å delta i andre foretak som driver tilsvarende virksomhet og for øvrig ethvert formål som har naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.5m in revenue and NOK 193,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.5m
Operating profit
NOK 193,000
Equity
NOK 1.4m
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns BÅLY BUNKRING AS?

NESEFISK AS
BÅLY BUNKRING AS
NOK 6.5m rev. · NOK 193,000 profit

BÅLY BUNKRING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BÅLY BUNKRING AS

Who owns BÅLY BUNKRING AS?

NESEFISK AS is the largest registered owner, with 33.4%.

What is the revenue of BÅLY BUNKRING AS?

BÅLY BUNKRING AS had revenue of NOK 6.5m in 2025.

Who is the general manager of BÅLY BUNKRING AS?

Jarle Fjeldskår is registered as general manager of BÅLY BUNKRING AS.

Where is BÅLY BUNKRING AS based?

BÅLY BUNKRING AS has its business address in Lindesnes.

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.