BIZTRAC BETA
Plumbing installation

NORDLAND RØR AS

Org. no. 936488315 Limited company (AS) Sortland Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 506,000
Operating profit NOK 73,000
Equity NOK 101,000
Incorporated 2025
Share capital NOK 45,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-10-20.

NORDLAND RØR AS is registered as a limited company in Sortland, Nordland with organisation number 936488315. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2025. Registered share capital is NOK 45,000, divided into 45000 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 506,000 in revenue and NOK 73,000 in operating profit.

Key figures · 2025

Revenue
NOK 506,000
Operating profit
NOK 73,000
Equity
NOK 101,000
Est. value
NOK 250,000

Financial health · 2025

Liquidity
1.44
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.7%
Good
Equity as a share of total capital

Who owns NORDLAND RØR AS?

JOAKIM BANADERA STRAND
NORDLAND RØR AS
NOK 506,000 rev. · NOK 73,000 profit

NORDLAND RØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORDLAND RØR AS

Who owns NORDLAND RØR AS?

JOAKIM BANADERA STRAND is the largest registered owner, with 100.0%.

What is the revenue of NORDLAND RØR AS?

NORDLAND RØR AS had revenue of NOK 506,000 in 2025.

Who is the general manager of NORDLAND RØR AS?

Joakim Banadera Strand is registered as general manager of NORDLAND RØR AS.

Where is NORDLAND RØR AS based?

NORDLAND RØR AS has its business address in Sortland.

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.