BIZTRAC BETA
Plumbing installation

VIBSTAD RØRSERVICE AS

Org. no. 935188660 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 81,000
Operating profit NOK −23,000
Equity NOK 968
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−23k kr).
  • Nylig endring 2026-07-01 Adresseendring registrert 2026-07-01.

VIBSTAD RØRSERVICE AS is registered as a limited company in Oslo, Oslo with organisation number 935188660. 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 100 shares. The company's stated purpose is: “Utføre rørleggertjenester og annen virksomhet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 81,000 in revenue and NOK −23,000 in operating profit.

Key figures · 2025

Revenue
NOK 81,000
Operating profit
NOK −23,000
Equity
NOK 968
Est. value
NOK 28,000

Financial health · 2025

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VIBSTAD RØRSERVICE AS?

SINDRE FJELDSETH VIBSTAD
VIBSTAD RØRSERVICE AS
NOK 81,000 rev. · NOK −23,000 profit

VIBSTAD RØRSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIBSTAD RØRSERVICE AS

Who owns VIBSTAD RØRSERVICE AS?

SINDRE FJELDSETH VIBSTAD is the largest registered owner, with 100.0%.

What is the revenue of VIBSTAD RØRSERVICE AS?

VIBSTAD RØRSERVICE AS had revenue of NOK 81,000 in 2025.

Where is VIBSTAD RØRSERVICE AS based?

VIBSTAD RØRSERVICE AS has its business address in Oslo.

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.