BIZTRAC BETA
Photographic activities

DERVO NATURKUNNSKAP AS

Org. no. 935932017 Limited company (AS) Lillehammer Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 52,000
Operating profit NOK 3,000
Equity NOK 27,000
Incorporated 2025
Share capital NOK 30,000

DERVO NATURKUNNSKAP AS is registered as a limited company in Lillehammer, Innlandet with organisation number 935932017. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Foredrag, forfattervirksomhet, fotografering og konsulentvirksomhet. og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 52,000 in revenue and NOK 3,000 in operating profit.

Key figures · 2025

Revenue
NOK 52,000
Operating profit
NOK 3,000
Equity
NOK 27,000
Est. value
NOK 37,000

Financial health · 2025

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

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

Who owns DERVO NATURKUNNSKAP AS?

BØRRE KIND DERVO
DERVO NATURKUNNSKAP AS
NOK 52,000 rev. · NOK 3,000 profit

DERVO NATURKUNNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DERVO NATURKUNNSKAP AS

Who owns DERVO NATURKUNNSKAP AS?

BØRRE KIND DERVO is the largest registered owner, with 100.0%.

What is the revenue of DERVO NATURKUNNSKAP AS?

DERVO NATURKUNNSKAP AS had revenue of NOK 52,000 in 2025.

Who is the general manager of DERVO NATURKUNNSKAP AS?

Børre Kind Dervo is registered as general manager of DERVO NATURKUNNSKAP AS.

Where is DERVO NATURKUNNSKAP AS based?

DERVO NATURKUNNSKAP AS has its business address in Lillehammer.

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.