BIZTRAC BETA
Buying and selling of own real estate

RINTO AS

Org. no. 987607378 Limited company (AS) Nesodden Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 300,000
Operating profit NOK 288,000
Equity NOK −109,000
Incorporated 2004
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−109k kr).

RINTO AS is registered as a limited company in Nesodden, Akershus with organisation number 987607378. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eie aksjer og andeler i andre selskap, foreta investeringer, eie og drive fast eiendom og drive konsulentvirksomhet samt hva står i forbindelse hermed.”. The most recent filed accounts, for the 2024 financial year, show NOK 300,000 in revenue and NOK 288,000 in operating profit.

Key figures · 2024

Revenue
NOK 300,000
Operating profit
NOK 288,000
Equity
NOK −109,000
Est. value
NOK 2.2m

Financial health · 2024

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

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

Who owns RINTO AS?

EINAR JOHAN HOLST
RINTO AS
NOK 300,000 rev. · NOK 288,000 profit

RINTO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RINTO AS

Who owns RINTO AS?

EINAR JOHAN HOLST is the largest registered owner, with 100.0%.

What is the revenue of RINTO AS?

RINTO AS had revenue of NOK 300,000 in 2024.

Who is the general manager of RINTO AS?

Einar Johan Holst is registered as general manager of RINTO AS.

Where is RINTO AS based?

RINTO AS has its business address in Nesoddtangen.

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.