BIZTRAC BETA
Plumbing installation

STIG RAGNAR EIENDOM AS

Org. no. 966218614 Limited company (AS) Indre Fosen Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 4.6m
Operating profit NOK 1.4m
Equity NOK 9.6m
Incorporated 1993
Share capital NOK 1.1m

STIG RAGNAR EIENDOM AS is registered as a limited company in Indre Fosen, Trøndelag with organisation number 966218614. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 1993. Registered share capital is NOK 1.1m, divided into 550 shares. The company's stated purpose is: “Eie og forvalte fast eiendom, samt delta i annen tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.6m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 4.6m
Operating profit
NOK 1.4m
Equity
NOK 9.6m
Est. value
NOK 8.2m

Financial health · 2024

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

Who owns STIG RAGNAR EIENDOM AS?

SR TUNG HOLDING AS
STIG RAGNAR EIENDOM AS
NOK 4.6m rev. · NOK 1.4m profit

STIG RAGNAR EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STIG RAGNAR EIENDOM AS own?

STIG RAGNAR EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STIG RAGNAR EIENDOM AS

Who owns STIG RAGNAR EIENDOM AS?

SR TUNG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of STIG RAGNAR EIENDOM AS?

STIG RAGNAR EIENDOM AS had revenue of NOK 4.6m in 2024.

Who is the general manager of STIG RAGNAR EIENDOM AS?

Stig Ragnar Tung is registered as general manager of STIG RAGNAR EIENDOM AS.

Where is STIG RAGNAR EIENDOM AS based?

STIG RAGNAR EIENDOM AS has its business address in Rissa.

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.