BIZTRAC BETA
Restaurant activities

EKEBY NOBEL AS

Org. no. 927609703 Limited company (AS) Moss Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 25,000
Equity NOK 31,000
Incorporated 2021
Employees 31
Share capital NOK 30,000

EKEBY NOBEL AS is registered as a limited company in Moss, Østfold with organisation number 927609703. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2021 and has 31 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Selskapets virksomhet er å eie og drive serveringssted/serveringslokaler, catering, delta i andre selskaper, annen matfaglig aktivitet, samt det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 25,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 25,000
Equity
NOK 31,000
Est. value
NOK 158,000

Financial health · 2024

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.3%
Weak
Equity as a share of total capital

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

Who owns EKEBY NOBEL AS?

EKEBY GÅRDSBRYGGERI AS
EKEBY NOBEL AS
NOK 1.4m rev. · NOK 25,000 profit

EKEBY NOBEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EKEBY NOBEL AS

Who owns EKEBY NOBEL AS?

EKEBY GÅRDSBRYGGERI AS is the largest registered owner, with 100.0%.

What is the revenue of EKEBY NOBEL AS?

EKEBY NOBEL AS had revenue of NOK 1.4m in 2024.

Who is the general manager of EKEBY NOBEL AS?

Finn-Erik Blakstad is registered as general manager of EKEBY NOBEL AS.

Where is EKEBY NOBEL AS based?

EKEBY NOBEL 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.