BIZTRAC BETA
Rental and operating of own or leased real estate

RIBAGO EIENDOM AS

Org. no. 917280320 Limited company (AS) Sør-Varanger Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 689,000
Equity NOK 1.3m
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RIBAGO EIENDOM AS is registered as a limited company in Sør-Varanger, Finnmark with organisation number 917280320. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å eie, leie ut og videreutvikle eiendommer, samt å investere i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 689,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 689,000
Equity
NOK 1.3m
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns RIBAGO EIENDOM AS?

RIBAGO AS
RIBAGO EIENDOM AS
NOK 2.2m rev. · NOK 689,000 profit

RIBAGO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RIBAGO EIENDOM AS

Who owns RIBAGO EIENDOM AS?

RIBAGO AS is the largest registered owner, with 100.0%.

What is the revenue of RIBAGO EIENDOM AS?

RIBAGO EIENDOM AS had revenue of NOK 2.2m in 2025.

Who is the general manager of RIBAGO EIENDOM AS?

Torild Sesseng is registered as general manager of RIBAGO EIENDOM AS.

Where is RIBAGO EIENDOM AS based?

RIBAGO EIENDOM AS has its business address in Kirkenes.

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.