biztrac. BETA
COMPANY REGISTER PROFILE
936349145 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

KIMIDA AS

Org. no. 936349145 Limited company (AS) Lillesand Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK −42
Equity NOK 23,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−42 kr).

KIMIDA AS is registered as a limited company in Lillesand, Agder with organisation number 936349145. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Bolig og eiendom, utvikling/ oppussing, salg, drift, utleie av bolig og eiendom, hagearbeid, samt annen virksomhet som står i naturlig sammenheng med dette. Verdipapirer og aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −42 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −42
Equity
NOK 23,000
Est. value
NOK 21,000

Financial health · 2025

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

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

Who owns KIMIDA AS?

KIMIDA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KIMIDA AS

Who owns KIMIDA AS?

Ida Møllen Stevense is the largest registered owner, with 50.0%.

What is the revenue of KIMIDA AS?

KIMIDA AS had revenue of NOK 0 in 2025.

Who is the general manager of KIMIDA AS?

Kim Ole Uhnger Møllen is registered as general manager of KIMIDA AS.

Where is KIMIDA AS based?

KIMIDA AS has its business address in Lillesand.

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.