BIZTRAC BETA
Site preparation

DYRKOLBOTN ENTREPRENØR AS

Org. no. 913300661 Limited company (AS) Bergen Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 10.1m
Operating profit NOK 1.6m
Equity NOK 414,000
Incorporated 2014
Employees 5
Share capital NOK 30,000

DYRKOLBOTN ENTREPRENØR AS is registered as a limited company in Bergen, Vestland with organisation number 913300661. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2014 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringer i aksjer, verdipapirer og eiendom, herav også deltakelse i andre selskaper, samt annen relatert virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.1m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 10.1m
Operating profit
NOK 1.6m
Equity
NOK 414,000
Est. value
NOK 4.8m

Financial health · 2024

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

Who owns DYRKOLBOTN ENTREPRENØR AS?

STÅLE EVJEN-DYRKOLBOTN
DYRKOLBOTN ENTREPRENØR AS
NOK 10.1m rev. · NOK 1.6m profit

DYRKOLBOTN ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DYRKOLBOTN ENTREPRENØR AS

Who owns DYRKOLBOTN ENTREPRENØR AS?

STÅLE EVJEN-DYRKOLBOTN is the largest registered owner, with 100.0%.

What is the revenue of DYRKOLBOTN ENTREPRENØR AS?

DYRKOLBOTN ENTREPRENØR AS had revenue of NOK 10.1m in 2024.

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

Ståle Evjen-Dyrkolbotn is registered as general manager of DYRKOLBOTN ENTREPRENØR AS.

Where is DYRKOLBOTN ENTREPRENØR AS based?

DYRKOLBOTN ENTREPRENØR AS has its business address in Hjellestad.

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.