BIZTRAC BETA
COMPANY REGISTER PROFILE
922591946 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 02.09.2026
Distilling, rectifying and blending of spirits

NORSTILL AS

Org. no. 922591946 Limited company (AS) Valle Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 44,000
Operating profit NOK −1.2m
Equity NOK −362,000
Incorporated 2019
Share capital NOK 222,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−362k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,2 mill kr).

NORSTILL AS is registered as a limited company in Valle, Agder with organisation number 922591946. The business is classified under distilling, rectifying and blending of spirits (NACE 11.010). The company was incorporated in 2019. Registered share capital is NOK 222,000, divided into 11112 shares. The company's stated purpose is: “Destillasjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 44,000 in revenue and NOK −1.2m in operating profit.

Key figures · 2025

Revenue
NOK 44,000
Operating profit
NOK −1.2m
▼ −522 %
Equity
NOK −362,000
▼ −150 %

Financial health · 2025

Liquidity
0.10
Not satisfactory
Current assets ÷ current liabilities
Profitability
-13.5%
Not satisfactory
Return on total assets
Solidity
-4.0%
Weak
Equity as a share of total capital

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

Who owns NORSTILL AS?

NORSTILL AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORSTILL AS

Who owns NORSTILL AS?

MENNESKELIGE RESURSER AS is the largest registered owner, with 45.0%.

What is the revenue of NORSTILL AS?

NORSTILL AS had revenue of NOK 44,000 in 2025.

Who is the general manager of NORSTILL AS?

Erik Berglihn is registered as general manager of NORSTILL AS.

Where is NORSTILL AS based?

NORSTILL AS has its business address in Valle.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.