BIZTRAC BETA
Activities at camp schools

DRAGEID LEIRSKOLE AS

Org. no. 981481992 Limited company (AS) Osen Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 7.8m
Operating profit NOK 1.0m
Equity NOK 12.2m
Incorporated 2000
Employees 21
Share capital NOK 100,000

DRAGEID LEIRSKOLE AS is registered as a limited company in Osen, Trøndelag with organisation number 981481992. The business is classified under activities at camp schools (NACE 85.596). The company was incorporated in 2000 and has 21 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drift av leirskole, kursvirksomhet og hva som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.8m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 7.8m
Operating profit
NOK 1.0m
Equity
NOK 12.2m
Est. value
NOK 12.6m

Financial health · 2025

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

Who owns DRAGEID LEIRSKOLE AS?

INGOLV DØRUM
DRAGEID LEIRSKOLE AS
NOK 7.8m rev. · NOK 1.0m profit

DRAGEID LEIRSKOLE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DRAGEID LEIRSKOLE AS own?

DRAGEID LEIRSKOLE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DRAGEID LEIRSKOLE AS

Who owns DRAGEID LEIRSKOLE AS?

INGOLV DØRUM is the largest registered owner, with 100.0%.

What is the revenue of DRAGEID LEIRSKOLE AS?

DRAGEID LEIRSKOLE AS had revenue of NOK 7.8m in 2025.

Who is the general manager of DRAGEID LEIRSKOLE AS?

Ingolv Dørum is registered as general manager of DRAGEID LEIRSKOLE AS.

Where is DRAGEID LEIRSKOLE AS based?

DRAGEID LEIRSKOLE AS has its business address in Seter.

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.