biztrac. BETA
COMPANY REGISTER PROFILE
935152445 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Plumbing installation

ROLVSØY RØR AS

Org. no. 935152445 Limited company (AS) Fredrikstad Incorporated 2025 Active
Revenue 2025 NOK 876,000
Operating profit NOK 144,000
Equity NOK 128,000
Incorporated 2025
Share capital NOK 30,000

ROLVSØY RØR AS is registered as a limited company in Fredrikstad, Østfold with organisation number 935152445. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen rørleggerarbeid og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 876,000 in revenue and NOK 144,000 in operating profit.

Key figures · 2025

Revenue
NOK 876,000
Operating profit
NOK 144,000
Equity
NOK 128,000
Est. value
NOK 490,000

Financial health · 2025

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

Who owns ROLVSØY RØR AS?

ROLVSØY RØR AS
NOK 876,000 rev. · NOK 144,000 profit

ROLVSØY RØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROLVSØY RØR AS

Who owns ROLVSØY RØR AS?

Ahmed Jassim Turaid Al-Shimary is the largest registered owner, with 100.0%.

What is the revenue of ROLVSØY RØR AS?

ROLVSØY RØR AS had revenue of NOK 876,000 in 2025.

Who is the general manager of ROLVSØY RØR AS?

Ahmed Jassim Turaid Al-Shimary is registered as general manager of ROLVSØY RØR AS.

Where is ROLVSØY RØR AS based?

ROLVSØY RØR 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.