BIZTRAC BETA
COMPANY REGISTER PROFILE
921268173 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

RITIRA AS

Org. no. 921268173 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 669,000
Operating profit NOK −334,000
Equity NOK −3.0m
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,0 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−334k kr).

RITIRA AS is registered as a limited company in Oslo, Oslo with organisation number 921268173. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utleie av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 669,000 in revenue and NOK −334,000 in operating profit.

Key figures · 2024

Revenue
NOK 669,000
Operating profit
NOK −334,000
Equity
NOK −3.0m

Financial health · 2024

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

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

Who owns RITIRA AS?

YENYUN FU
RITIRA AS
NOK 669,000 rev. · NOK −334,000 profit

RITIRA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RITIRA AS

Who owns RITIRA AS?

YENYUN FU is the largest registered owner, with 100.0%.

What is the revenue of RITIRA AS?

RITIRA AS had revenue of NOK 669,000 in 2024.

Who is the general manager of RITIRA AS?

Man Li Fu Tsao is registered as general manager of RITIRA AS.

Where is RITIRA AS based?

RITIRA AS has its business address in Oslo.

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.