BIZTRAC BETA
Wholesale of tobacco products

365ECOM AS

Org. no. 927964589 Limited company (AS) Asker Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −50,000
Equity NOK 393,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

365ECOM AS is registered as a limited company in Asker, Akershus with organisation number 927964589. The business is classified under wholesale of tobacco products (NACE 46.350). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Import og handel med konsumentvarer, herunder handel med tobakksvarer, og dertil tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −50,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −50,000
Equity
NOK 393,000
Est. value
NOK 34.8m

Financial health · 2025

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

Who owns 365ECOM AS?

MOIV AS
365ECOM AS
NOK 0 rev. · NOK −50,000 profit

365ECOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does 365ECOM AS own?

365ECOM AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

365ECOM AS er morselskap for 2 datterselskaper:

Frequently asked questions about 365ECOM AS

Who owns 365ECOM AS?

MOIV AS is the largest registered owner, with 33.3%.

What is the revenue of 365ECOM AS?

365ECOM AS had revenue of NOK 0 in 2025.

Who is the general manager of 365ECOM AS?

Morten Iversen Huer is registered as general manager of 365ECOM AS.

Where is 365ECOM AS based?

365ECOM AS has its business address in Slemmestad.

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.