biztrac. BETA
COMPANY REGISTER PROFILE
930736007 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Wholesale of coffee, tea, cocoa and spices

ESPRESSO CATERING AS

Org. no. 930736007 Limited company (AS) Stavanger Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 147,000
Equity NOK 290,000
Incorporated 2022
Share capital NOK 30,000

ESPRESSO CATERING AS is registered as a limited company in Stavanger, Rogaland with organisation number 930736007. The business is classified under wholesale of coffee, tea, cocoa and spices (NACE 46.370). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kaffecatering, kaffeimport, kaffesalg på nett, engros og detaljhandel.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 147,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
▲ +83 %
Operating profit
NOK 147,000
▼ −2 %
Equity
NOK 290,000
▲ +52 %
Est. value
NOK 587,000

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
25.9%
Very good
Return on total assets
Solidity
47.7%
Very good
Equity as a share of total capital

Who owns ESPRESSO CATERING AS?

ESPRESSO CATERING AS
NOK 1.3m rev. · NOK 147,000 profit

ESPRESSO CATERING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ESPRESSO CATERING AS

Who owns ESPRESSO CATERING AS?

Nataliia Skuba is the largest registered owner, with 50.0%.

What is the revenue of ESPRESSO CATERING AS?

ESPRESSO CATERING AS had revenue of NOK 1.3m in 2025.

Who is the general manager of ESPRESSO CATERING AS?

Sergii Lukianenko is registered as general manager of ESPRESSO CATERING AS.

Where is ESPRESSO CATERING AS based?

ESPRESSO CATERING AS has its business address in Bru.

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.