BIZTRAC BETA
Restaurant activities

RINGEBU KRO AS

Org. no. 916212283 Limited company (AS) Ringebu Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK −34,000
Equity NOK −290,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

RINGEBU KRO AS is registered as a limited company in Ringebu, Innlandet with organisation number 916212283. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drift av restaurant/kafe/gatekjøkken og det som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK −34,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK −34,000
Equity
NOK −290,000

Financial health · 2025

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

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

Who owns RINGEBU KRO AS?

SEHRISH MAHMOOD
RINGEBU KRO AS
NOK 2.2m rev. · NOK −34,000 profit

RINGEBU KRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RINGEBU KRO AS

Who owns RINGEBU KRO AS?

SEHRISH MAHMOOD is the largest registered owner, with 100.0%.

What is the revenue of RINGEBU KRO AS?

RINGEBU KRO AS had revenue of NOK 2.2m in 2025.

Who is the general manager of RINGEBU KRO AS?

Sehrish Mahmood is registered as general manager of RINGEBU KRO AS.

Where is RINGEBU KRO AS based?

RINGEBU KRO AS has its business address in Ringebu.

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.