BIZTRAC BETA
Site preparation

NERDAL ENTREPRENØR AS

Org. no. 918553428 Limited company (AS) Gulen Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 7.6m
Operating profit NOK 265,000
Equity NOK 822,000
Incorporated 2017
Share capital NOK 30,000

NERDAL ENTREPRENØR AS is registered as a limited company in Gulen, Vestland with organisation number 918553428. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Arbeid med gravemaskin og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.6m in revenue and NOK 265,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.6m
Operating profit
NOK 265,000
Equity
NOK 822,000
Est. value
NOK 1.3m

Financial health · 2024

Liquidity
1.60
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.1%
Good
Equity as a share of total capital

Who owns NERDAL ENTREPRENØR AS?

ROY NERDAL
NERDAL ENTREPRENØR AS
NOK 7.6m rev. · NOK 265,000 profit

NERDAL ENTREPRENØR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NERDAL ENTREPRENØR AS

Who owns NERDAL ENTREPRENØR AS?

ROY NERDAL is the largest registered owner, with 50.0%.

What is the revenue of NERDAL ENTREPRENØR AS?

NERDAL ENTREPRENØR AS had revenue of NOK 7.6m in 2024.

Who is the general manager of NERDAL ENTREPRENØR AS?

Bjarte Neset Nerdal is registered as general manager of NERDAL ENTREPRENØR AS.

Where is NERDAL ENTREPRENØR AS based?

NERDAL ENTREPRENØR AS has its business address in Dalsøyra.

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.