BIZTRAC BETA
Restaurant activities

CREPERI TO BE AS

Org. no. 927425114 Limited company (AS) Porsgrunn Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK −571,000
Equity NOK −199,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−199k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−571k kr).

CREPERI TO BE AS is registered as a limited company in Porsgrunn, Telemark with organisation number 927425114. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Restaurantvirksomhet og det som naturlig hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK −571,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK −571,000
Equity
NOK −199,000

Financial health · 2025

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-41.3%
Weak
Equity as a share of total capital

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

Who owns CREPERI TO BE AS?

BASHKIM GODUNI
CREPERI TO BE AS
NOK 1.5m rev. · NOK −571,000 profit

CREPERI TO BE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CREPERI TO BE AS

Who owns CREPERI TO BE AS?

BASHKIM GODUNI is the largest registered owner, with 100.0%.

What is the revenue of CREPERI TO BE AS?

CREPERI TO BE AS had revenue of NOK 1.5m in 2025.

Who is the general manager of CREPERI TO BE AS?

Bashkim Goduni is registered as general manager of CREPERI TO BE AS.

Where is CREPERI TO BE AS based?

CREPERI TO BE AS has its business address in Porsgrunn.

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.