BIZTRAC BETA
Repair and maintenance of machinery

BOTNEDALEN DOSARLAG AS

Org. no. 834962772 Limited company (AS) Tokke Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 120,000
Operating profit NOK 38,000
Equity NOK 57,000
Incorporated 2024
Share capital NOK 30,000

BOTNEDALEN DOSARLAG AS is registered as a limited company in Tokke, Telemark with organisation number 834962772. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 150 shares. The company's stated purpose is: “Løypevedlikehold, utleige av maskiner, personell, reparasjonar og alt som fell naturleg inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 120,000 in revenue and NOK 38,000 in operating profit.

Key figures · 2025

Revenue
NOK 120,000
Operating profit
NOK 38,000
Equity
NOK 57,000
Est. value
NOK 133,000

Financial health · 2025

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

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

Who owns BOTNEDALEN DOSARLAG AS?

HÅKON RYKKELID
BOTNEDALEN DOSARLAG AS
NOK 120,000 rev. · NOK 38,000 profit

BOTNEDALEN DOSARLAG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BOTNEDALEN DOSARLAG AS

Who owns BOTNEDALEN DOSARLAG AS?

HÅKON RYKKELID is the largest registered owner, with 33.3%.

What is the revenue of BOTNEDALEN DOSARLAG AS?

BOTNEDALEN DOSARLAG AS had revenue of NOK 120,000 in 2025.

Who is the general manager of BOTNEDALEN DOSARLAG AS?

Håkon Rykkelid is registered as general manager of BOTNEDALEN DOSARLAG AS.

Where is BOTNEDALEN DOSARLAG AS based?

BOTNEDALEN DOSARLAG AS has its business address in Dalen.

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.