BIZTRAC BETA
Manufacture of beer

GEIRANGER BRYGGERI AS

Org. no. 914497264 Limited company (AS) Stranda Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 88,000
Equity NOK 2.5m
Incorporated 2014
Share capital NOK 1.4m

GEIRANGER BRYGGERI AS is registered as a limited company in Stranda, Møre og Romsdal with organisation number 914497264. The business is classified under manufacture of beer (NACE 11.050). The company was incorporated in 2014. Registered share capital is NOK 1.4m, divided into 1450 shares. The company's stated purpose is: “Drift av mikrobryggeri for øl og andre produkt/tjenester som naturleg høyrer saman med dette, under dette å ta del i andre selskap med liknande verksemd, og kjøp og sal av aksjar eller på annan måte gjere seg interessert i andre føretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 88,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 88,000
Equity
NOK 2.5m
Est. value
NOK 1.5m

Financial health · 2024

Liquidity
1.00
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.1%
Good
Equity as a share of total capital

Who owns GEIRANGER BRYGGERI AS?

FRANK MARÅK
GEIRANGER BRYGGERI AS
NOK 2.6m rev. · NOK 88,000 profit

GEIRANGER BRYGGERI AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about GEIRANGER BRYGGERI AS

Who owns GEIRANGER BRYGGERI AS?

FRANK MARÅK is the largest registered owner, with 58.6%.

What is the revenue of GEIRANGER BRYGGERI AS?

GEIRANGER BRYGGERI AS had revenue of NOK 2.6m in 2025.

Who is the general manager of GEIRANGER BRYGGERI AS?

Frank Maråk is registered as general manager of GEIRANGER BRYGGERI AS.

Where is GEIRANGER BRYGGERI AS based?

GEIRANGER BRYGGERI AS has its business address in Geiranger.

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.