BIZTRAC BETA
COMPANY REGISTER PROFILE
928652718 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Other technical consultancy

BASTEVOLLEN AS

Org. no. 928652718 Limited company (AS) Flekkefjord Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 400,000
Operating profit NOK −77,000
Equity NOK 2.1m
Incorporated 2022
Share capital NOK 30,000

Signals

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

BASTEVOLLEN AS is registered as a limited company in Flekkefjord, Agder with organisation number 928652718. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rådgivning og konsulenttjenester for energibransjen. Investering i aksjer og eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 400,000 in revenue and NOK −77,000 in operating profit.

Key figures · 2025

Revenue
NOK 400,000
Operating profit
NOK −77,000
Equity
NOK 2.1m
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns BASTEVOLLEN AS?

KJELL OLAF HOEL
BASTEVOLLEN AS
NOK 400,000 rev. · NOK −77,000 profit

BASTEVOLLEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BASTEVOLLEN AS

Who owns BASTEVOLLEN AS?

KJELL OLAF HOEL is the largest registered owner, with 50.0%.

What is the revenue of BASTEVOLLEN AS?

BASTEVOLLEN AS had revenue of NOK 400,000 in 2025.

Who is the general manager of BASTEVOLLEN AS?

Kjell Olaf Hoel is registered as general manager of BASTEVOLLEN AS.

Where is BASTEVOLLEN AS based?

BASTEVOLLEN AS has its business address in Gyland.

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.