BIZTRAC BETA
Rental and operating of own or leased real estate

IN-CITO AS

Org. no. 942146469 Limited company (AS) Ålesund Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 672,000
Equity NOK 27.0m
Incorporated 1987
Share capital NOK 3.2m

IN-CITO AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 942146469. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1987. Registered share capital is NOK 3.2m, divided into 916 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av fast eiendom. Sel- skapet kan som aksjonær eller interessent på annen måte delta i andre selskap med økonomisk virksom- het som formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 672,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 672,000
Equity
NOK 27.0m
Est. value
NOK 20.6m

Financial health · 2024

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

Who owns IN-CITO AS?

OVE KNUT FJØRTOFT
IN-CITO AS
NOK 1.6m rev. · NOK 672,000 profit

IN-CITO AS has 3 registered shareholders:

All shareholders and roles →

Which companies does IN-CITO AS own?

IN-CITO AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about IN-CITO AS

Who owns IN-CITO AS?

OVE KNUT FJØRTOFT is the largest registered owner, with 53.1%.

What is the revenue of IN-CITO AS?

IN-CITO AS had revenue of NOK 1.6m in 2024.

Who is the general manager of IN-CITO AS?

Cathrin Fjørtoft is registered as general manager of IN-CITO AS.

Where is IN-CITO AS based?

IN-CITO AS has its business address in Ålesund.

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.