biztrac. BETA
COMPANY REGISTER PROFILE
999311202 ORG. NO. 2025 ACCOUNTS 12 SECTIONS
Active UPDATED 03.10.2026
Manufacture of beer

SMÅ VESEN AS

Org. no. 999311202 Limited company (AS) Nord-Aurdal Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 5.7m
Operating profit NOK 346,000
Equity NOK 116,000
Incorporated 2012
Employees 5
Share capital NOK 1.2m

SMÅ VESEN AS is registered as a limited company in Nord-Aurdal, Innlandet with organisation number 999311202. The business is classified under manufacture of beer (NACE 11.050). The company was incorporated in 2012 and has 5 registered employees. Registered share capital is NOK 1.2m, divided into 1200 shares. The company's stated purpose is: “Drive bryggerivirksomhet, og hva dermed står i forbindelse - herunder salg foruten investering og deltagelse i selskap med samme formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.7m in revenue and NOK 346,000 in operating profit.

Former names: SMÅ VESEN BRYGGERI AS, VALDRES MIKROBRYGGERI AS

Key figures · 2025

Revenue
NOK 5.7m
▲ +20 %
Operating profit
NOK 346,000
▲ +773 %
Equity
NOK 116,000
▲ +224 %
Est. value
NOK 350,000

Financial health · 2025

Liquidity
1.64
Good
Current assets ÷ current liabilities
Profitability
7.3%
Satisfactory
Return on total assets
Solidity
2.3%
Not satisfactory
Equity as a share of total capital

Who owns SMÅ VESEN AS?

SMÅ VESEN AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SMÅ VESEN AS

Who owns SMÅ VESEN AS?

Knut A Kulhuset is the largest registered owner, with 25.0%.

What is the revenue of SMÅ VESEN AS?

SMÅ VESEN AS had revenue of NOK 5.7m in 2025.

Who is the general manager of SMÅ VESEN AS?

Espen Kristoffer Bakken Blåfjelldal is registered as general manager of SMÅ VESEN AS.

Where is SMÅ VESEN AS based?

SMÅ VESEN AS has its business address in Aurdal.

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.