BIZTRAC BETA
Rental and operating of own or leased real estate

SOLID NÆRINGSEIENDOM AS

Org. no. 982365074 Limited company (AS) Fredrikstad Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 81,000
Equity NOK 5.0m
Incorporated 2000
Share capital NOK 64,000

SOLID NÆRINGSEIENDOM AS is registered as a limited company in Fredrikstad, Østfold with organisation number 982365074. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2000. Registered share capital is NOK 64,000, divided into 64 shares. The company's stated purpose is: “Kjøp, salg og drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 81,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 81,000
Equity
NOK 5.0m
Est. value
NOK 3.6m

Financial health · 2025

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

Who owns SOLID NÆRINGSEIENDOM AS?

SOLID EIENDOM AS
SOLID NÆRINGSEIENDOM AS
NOK 1.2m rev. · NOK 81,000 profit

SOLID NÆRINGSEIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SOLID NÆRINGSEIENDOM AS own?

SOLID NÆRINGSEIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Group structure

SOLID NÆRINGSEIENDOM AS er morselskap for 4 datterselskaper:

Frequently asked questions about SOLID NÆRINGSEIENDOM AS

Who owns SOLID NÆRINGSEIENDOM AS?

SOLID EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of SOLID NÆRINGSEIENDOM AS?

SOLID NÆRINGSEIENDOM AS had revenue of NOK 1.2m in 2025.

Where is SOLID NÆRINGSEIENDOM AS based?

SOLID NÆRINGSEIENDOM AS has its business address in Rolvsøy.

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.