BIZTRAC BETA
Event catering activities

CELESTA BRYNE AS

Org. no. 925592277 Limited company (AS) Time Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 6.0m
Operating profit NOK 322,000
Equity NOK 979,000
Incorporated 2020
Employees 14
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

CELESTA BRYNE AS is registered as a limited company in Time, Rogaland with organisation number 925592277. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2020 and has 14 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Produksjon og salg av pizza ved catering og takeaway.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.0m in revenue and NOK 322,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.0m
Operating profit
NOK 322,000
Equity
NOK 979,000
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns CELESTA BRYNE AS?

BANKERS HOLDING AS
CELESTA BRYNE AS
NOK 6.0m rev. · NOK 322,000 profit

CELESTA BRYNE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CELESTA BRYNE AS

Who owns CELESTA BRYNE AS?

BANKERS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of CELESTA BRYNE AS?

CELESTA BRYNE AS had revenue of NOK 6.0m in 2024.

Who is the general manager of CELESTA BRYNE AS?

Lilly Sirevåg Søyland is registered as general manager of CELESTA BRYNE AS.

Where is CELESTA BRYNE AS based?

CELESTA BRYNE AS has its business address in Bryne.

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.