BIZTRAC BETA
Rental and operating of own or leased real estate

TOSI EIENDOM AS

Org. no. 981136713 Limited company (AS) Namsos Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 416,000
Operating profit NOK 141,000
Equity NOK 2.1m
Incorporated 1999
Share capital NOK 650,000

TOSI EIENDOM AS is registered as a limited company in Namsos, Trøndelag with organisation number 981136713. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. Registered share capital is NOK 650,000, divided into 650 shares. The company's stated purpose is: “Handel, kjøp, salg og utleie av eiendommer og andre driftsmidler, bygge- og anleggsvirksomhet, kjøp og salg av verdipapirer, samt ved aksjer eller på annen måte delta i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 416,000 in revenue and NOK 141,000 in operating profit.

Key figures · 2024

Revenue
NOK 416,000
Operating profit
NOK 141,000
Equity
NOK 2.1m
Est. value
NOK 1.9m

Financial health · 2024

Liquidity
14.52
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
97.9%
Very good
Equity as a share of total capital

Who owns TOSI EIENDOM AS?

SIRI HILDEGUNN OLSEN EINSETH
TOSI EIENDOM AS
NOK 416,000 rev. · NOK 141,000 profit

TOSI EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TOSI EIENDOM AS

Who owns TOSI EIENDOM AS?

SIRI HILDEGUNN OLSEN EINSETH is the largest registered owner, with 50.0%.

What is the revenue of TOSI EIENDOM AS?

TOSI EIENDOM AS had revenue of NOK 416,000 in 2024.

Who is the general manager of TOSI EIENDOM AS?

Torgeir Einseth is registered as general manager of TOSI EIENDOM AS.

Where is TOSI EIENDOM AS based?

TOSI EIENDOM AS has its business address in Namsos.

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.