BIZTRAC BETA
Rental and operating of own or leased real estate

CHIRO INVEST AS

Org. no. 997391616 Limited company (AS) Sortland Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 755,000
Operating profit NOK 610,000
Equity NOK 3.2m
Incorporated 2011
Share capital NOK 100,000

CHIRO INVEST AS is registered as a limited company in Sortland, Nordland with organisation number 997391616. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å investere i eiendom og andre selskaper, utleie av eiendom, forvaltning av selskapets midler gjennom ulike finansielle plasseringer, samt annen virksomhet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 755,000 in revenue and NOK 610,000 in operating profit.

Key figures · 2025

Revenue
NOK 755,000
Operating profit
NOK 610,000
Equity
NOK 3.2m
Est. value
NOK 3.5m

Financial health · 2024

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

Who owns CHIRO INVEST AS?

LARS TORBJØRN DRAGLAND
CHIRO INVEST AS
NOK 755,000 rev. · NOK 610,000 profit

CHIRO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CHIRO INVEST AS

Who owns CHIRO INVEST AS?

LARS TORBJØRN DRAGLAND is the largest registered owner, with 100.0%.

What is the revenue of CHIRO INVEST AS?

CHIRO INVEST AS had revenue of NOK 755,000 in 2025.

Who is the general manager of CHIRO INVEST AS?

Lars Torbjørn Dragland is registered as general manager of CHIRO INVEST AS.

Where is CHIRO INVEST AS based?

CHIRO INVEST AS has its business address in Sortland.

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.