biztrac. BETA
COMPANY REGISTER PROFILE
931239392 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Distilling, rectifying and blending of spirits

STRÆTÅSEN AKEVITTLAG AS

Org. no. 931239392 Limited company (AS) Våler Incorporated 2023 Active
Operating profit NOK −7,000
Equity NOK −10,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−10k kr).

STRÆTÅSEN AKEVITTLAG AS is registered as a limited company in Våler, Innlandet with organisation number 931239392. The business is classified under distilling, rectifying and blending of spirits (NACE 11.010). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 102 shares. The company's stated purpose is: “Foredling og salg av akevitt. Samt deltagelse i andre selskaper og annen virksomhet som naturlig faller inn under dette.”.

Key figures · 2025

Operating profit
NOK −7,000
▲ +1 %
Equity
NOK −10,000
▼ −181 %

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-2.8%
Weak
Equity as a share of total capital

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

Who owns STRÆTÅSEN AKEVITTLAG AS?

STRÆTÅSEN AKEVITTLAG AS has 6 registered shareholders:

All shareholders and roles →

Which companies does STRÆTÅSEN AKEVITTLAG AS own?

STRÆTÅSEN AKEVITTLAG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STRÆTÅSEN AKEVITTLAG AS

Who owns STRÆTÅSEN AKEVITTLAG AS?

Arne Aasmund Skarderud is the largest registered owner, with 16.7%.

Who is the general manager of STRÆTÅSEN AKEVITTLAG AS?

Hein Eriksen is registered as general manager of STRÆTÅSEN AKEVITTLAG AS.

Where is STRÆTÅSEN AKEVITTLAG AS based?

STRÆTÅSEN AKEVITTLAG AS has its business address in Braskereidfoss.

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.