BIZTRAC BETA
COMPANY REGISTER PROFILE
995073978 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Non-specialised retail sale of predominately food, beverages or tobacco

JOKER RYFOSS AS

Org. no. 995073978 Limited company (AS) Vang Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 21.1m
Operating profit NOK 256,000
Equity NOK 4.2m
Incorporated 2010
Employees 12
Share capital NOK 100,000

JOKER RYFOSS AS is registered as a limited company in Vang, Innlandet with organisation number 995073978. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2010 and has 12 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Sal av daglegvarer og det som naturleg høyrer til.”. The most recent filed accounts, for the 2025 financial year, show NOK 21.1m in revenue and NOK 256,000 in operating profit.

Key figures · 2025

Revenue
NOK 21.1m
▲ +3 %
Operating profit
NOK 256,000
▼ −55 %
Equity
NOK 4.2m
▲ +3 %
Est. value
NOK 3.1m

Financial health · 2025

Liquidity
3.81
Very good
Current assets ÷ current liabilities
Profitability
3.5%
Weak
Return on total assets
Solidity
55.1%
Very good
Equity as a share of total capital

Who owns JOKER RYFOSS AS?

JOKER RYFOSS AS
NOK 21.1m rev. · NOK 256,000 profit

JOKER RYFOSS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JOKER RYFOSS AS

Who owns JOKER RYFOSS AS?

MONICA LITANGEN is the largest registered owner, with 50.0%.

What is the revenue of JOKER RYFOSS AS?

JOKER RYFOSS AS had revenue of NOK 21.1m in 2025.

Who is the general manager of JOKER RYFOSS AS?

Monica Litangen is registered as general manager of JOKER RYFOSS AS.

Where is JOKER RYFOSS AS based?

JOKER RYFOSS AS has its business address in Ryfoss.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.