biztrac. BETA
COMPANY REGISTER PROFILE
916650647 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Photographic activities

ORGANISK RÅDGIVNING AS

Org. no. 916650647 Limited company (AS) Trondheim Incorporated 2016 Active
Revenue 2025 NOK 603,000
Operating profit NOK 45,000
Equity NOK 107,000
Incorporated 2016
Share capital NOK 30,000

ORGANISK RÅDGIVNING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 916650647. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Dronetjenester og virksomhet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 603,000 in revenue and NOK 45,000 in operating profit.

Former names: DRONEAIR AS

Key figures · 2025

Revenue
NOK 603,000
▲ +3 %
Operating profit
NOK 45,000
▲ +118 %
Equity
NOK 107,000
▲ +61 %
Est. value
NOK 240,000

Financial health · 2025

Liquidity
1.98
Good
Current assets ÷ current liabilities
Profitability
19.7%
Very good
Return on total assets
Solidity
49.5%
Very good
Equity as a share of total capital

Who owns ORGANISK RÅDGIVNING AS?

ORGANISK RÅDGIVNING AS
NOK 603,000 rev. · NOK 45,000 profit

ORGANISK RÅDGIVNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ORGANISK RÅDGIVNING AS

Who owns ORGANISK RÅDGIVNING AS?

Lone Endresen Moa is the largest registered owner, with 100.0%.

What is the revenue of ORGANISK RÅDGIVNING AS?

ORGANISK RÅDGIVNING AS had revenue of NOK 603,000 in 2025.

Who is the general manager of ORGANISK RÅDGIVNING AS?

Thomas Eidsaune is registered as general manager of ORGANISK RÅDGIVNING AS.

Where is ORGANISK RÅDGIVNING AS based?

ORGANISK RÅDGIVNING AS has its business address in Trondheim.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.