BIZTRAC BETA
Growing of pome fruits and stone fruits

CHILI HAVEN AS

Org. no. 936282938 Limited company (AS) Eidsvoll Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 28,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-09-29.

CHILI HAVEN AS is registered as a limited company in Eidsvoll, Akershus with organisation number 936282938. The business is classified under growing of pome fruits and stone fruits (NACE 01.240). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Produksjon av gårdsprodukter - Med mye fokus på Chili .”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 28,000
Est. value
NOK 26,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 CHILI HAVEN AS?

KRISTIAN ALEKSANDER MOE
CHILI HAVEN AS
NOK 0 rev. · NOK −2,000 profit

CHILI HAVEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CHILI HAVEN AS

Who owns CHILI HAVEN AS?

KRISTIAN ALEKSANDER MOE is the largest registered owner, with 100.0%.

What is the revenue of CHILI HAVEN AS?

CHILI HAVEN AS had revenue of NOK 0 in 2025.

Who is the general manager of CHILI HAVEN AS?

Kristian Aleksander Moe is registered as general manager of CHILI HAVEN AS.

Where is CHILI HAVEN AS based?

CHILI HAVEN AS has its business address in Eidsvoll.

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.