BIZTRAC BETA
Restaurant activities

COFFEE CORNER AS

Org. no. 926297791 Limited company (AS) Klepp Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK 335,000
Equity NOK 503,000
Incorporated 2020
Employees 7
Share capital NOK 30,000

COFFEE CORNER AS is registered as a limited company in Klepp, Rogaland with organisation number 926297791. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2020 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift av restauranter og kafeer og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.9m in revenue and NOK 335,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
Operating profit
NOK 335,000
Equity
NOK 503,000
Est. value
NOK 1.5m

Financial health · 2024

Liquidity
1.26
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.3%
Good
Equity as a share of total capital

Who owns COFFEE CORNER AS?

RASMUS SELE
COFFEE CORNER AS
NOK 3.9m rev. · NOK 335,000 profit

COFFEE CORNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about COFFEE CORNER AS

Who owns COFFEE CORNER AS?

RASMUS SELE is the largest registered owner, with 100.0%.

What is the revenue of COFFEE CORNER AS?

COFFEE CORNER AS had revenue of NOK 3.9m in 2025.

Who is the general manager of COFFEE CORNER AS?

Rasmus Sele is registered as general manager of COFFEE CORNER AS.

Where is COFFEE CORNER AS based?

COFFEE CORNER AS has its business address in Kleppe.

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.