BIZTRAC BETA
Distilling, rectifying and blending of spirits

NUET AS

Org. no. 921687443 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK −3.2m
Equity NOK 994,000
Incorporated 2018
Employees 7
Share capital NOK 215,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3,2 mill kr).
  • Nylig endring 2026-06-29 Adresseendring registrert 2026-06-29.

NUET AS is registered as a limited company in Oslo, Oslo with organisation number 921687443. The business is classified under distilling, rectifying and blending of spirits (NACE 11.010). The company was incorporated in 2018 and has 7 registered employees. Registered share capital is NOK 215,000, divided into 215078 shares. The company's stated purpose is: “Produksjon, import og salg av akevitt og andre alkoholholdige og ikke alkoholholdige drikkevarer, såvel som investeringer i eiendom og verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK −3.2m in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK −3.2m
Equity
NOK 994,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns NUET AS?

LYNX INVESTMENTS AS
NUET AS
NOK 1.3m rev. · NOK −3.2m profit

NUET AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about NUET AS

Who owns NUET AS?

LYNX INVESTMENTS AS is the largest registered owner, with 48.8%.

What is the revenue of NUET AS?

NUET AS had revenue of NOK 1.3m in 2025.

Who is the general manager of NUET AS?

Ingvild Nilsen Helle is registered as general manager of NUET AS.

Where is NUET AS based?

NUET AS has its business address in Oslo.

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.