biztrac. BETA
COMPANY REGISTER PROFILE
934120396 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

NIMATI AS

Org. no. 934120396 Limited company (AS) Kvinesdal Incorporated 2024 Active
Revenue 2025 NOK 106,000
Operating profit NOK −451
Equity NOK 7,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

NIMATI AS is registered as a limited company in Kvinesdal, Agder with organisation number 934120396. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Butikk som skal selge hjemmelaga ting, samt leie ut hylleplass i lokalet.”. The most recent filed accounts, for the 2025 financial year, show NOK 106,000 in revenue and NOK −451 in operating profit.

Key figures · 2025

Revenue
NOK 106,000
▼ −1 %
Operating profit
NOK −451
▲ +93 %
Equity
NOK 7,000
▲ +700 %
Est. value
NOK 164,000

Financial health · 2025

Liquidity
1.73
Good
Current assets ÷ current liabilities
Profitability
-3.7%
Not satisfactory
Return on total assets
Solidity
42.3%
Weak
Equity as a share of total capital

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

Who owns NIMATI AS?

NIMATI AS
NOK 106,000 rev. · NOK −451 profit

NIMATI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NIMATI AS

Who owns NIMATI AS?

Jan Tommy Kila is the largest registered owner, with 50.0%.

What is the revenue of NIMATI AS?

NIMATI AS had revenue of NOK 106,000 in 2025.

Who is the general manager of NIMATI AS?

Jan Tommy Kila is registered as general manager of NIMATI AS.

Where is NIMATI AS based?

NIMATI AS has its business address in Feda.

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.