BIZTRAC BETA
Other specialised construction activities in construction of buildings

2DRILL AS

Org. no. 932688956 Limited company (AS) Nærøysund Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK −222,000
Equity NOK 25,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

2DRILL AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 932688956. The business is classified under other specialised construction activities in construction of buildings (NACE 43.420). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Boring i faste og løse masser for sprenging, fundamentering og injeksjon, samt arbeider tilknyttet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK −222,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK −222,000
Equity
NOK 25,000
Est. value
NOK 763,000

Financial health · 2025

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.4%
Weak
Equity as a share of total capital

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

Who owns 2DRILL AS?

JULEDAGEN AS
2DRILL AS
NOK 2.2m rev. · NOK −222,000 profit

2DRILL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about 2DRILL AS

Who owns 2DRILL AS?

JULEDAGEN AS is the largest registered owner, with 100.0%.

What is the revenue of 2DRILL AS?

2DRILL AS had revenue of NOK 2.2m in 2025.

Who is the general manager of 2DRILL AS?

Arthur Gisle Norheim is registered as general manager of 2DRILL AS.

Where is 2DRILL AS based?

2DRILL AS has its business address in Kolvereid.

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.