BIZTRAC BETA
Manufacture of beer

EKEBY GÅRDSBRYGGERI AS

Org. no. 923088881 Limited company (AS) Moss Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 5.2m
Operating profit NOK −1.3m
Equity NOK 2.5m
Incorporated 2019
Employees 5
Share capital NOK 45,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,3 mill kr).

EKEBY GÅRDSBRYGGERI AS is registered as a limited company in Moss, Østfold with organisation number 923088881. The business is classified under manufacture of beer (NACE 11.050). The company was incorporated in 2019 and has 5 registered employees. Registered share capital is NOK 45,000, divided into 301821 shares. The company's stated purpose is: “Produksjon, salg og servering av øl, samt delta i andre selskaper og virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.2m in revenue and NOK −1.3m in operating profit.

Key figures · 2024

Revenue
NOK 5.2m
Operating profit
NOK −1.3m
Equity
NOK 2.5m
Est. value
NOK 3.6m

Financial health · 2024

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

Who owns EKEBY GÅRDSBRYGGERI AS?

FABELASTISK AS
EKEBY GÅRDSBRYGGERI AS
NOK 5.2m rev. · NOK −1.3m profit

EKEBY GÅRDSBRYGGERI AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does EKEBY GÅRDSBRYGGERI AS own?

EKEBY GÅRDSBRYGGERI AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about EKEBY GÅRDSBRYGGERI AS

Who owns EKEBY GÅRDSBRYGGERI AS?

FABELASTISK AS is the largest registered owner, with 22.7%.

What is the revenue of EKEBY GÅRDSBRYGGERI AS?

EKEBY GÅRDSBRYGGERI AS had revenue of NOK 5.2m in 2024.

Where is EKEBY GÅRDSBRYGGERI AS based?

EKEBY GÅRDSBRYGGERI AS has its business address in Dilling.

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.