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

SR RØR OG BAD AS

Org. no. 935233569 Limited company (AS) Lillestrøm Incorporated 2025 Active
Revenue 2025 NOK 452,000
Operating profit NOK 211,000
Equity NOK 190,000
Incorporated 2025
Share capital NOK 30,000

SR RØR OG BAD AS is registered as a limited company in Lillestrøm, Akershus with organisation number 935233569. 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 452,000 in revenue and NOK 211,000 in operating profit.

Key figures · 2025

Revenue
NOK 452,000
Operating profit
NOK 211,000
Equity
NOK 190,000
Est. value
NOK 705,000

Financial health · 2025

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

Who owns SR RØR OG BAD AS?

SR RØR OG BAD AS
NOK 452,000 rev. · NOK 211,000 profit

SR RØR OG BAD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SR RØR OG BAD AS

Who owns SR RØR OG BAD AS?

Nahom Mekonen Tzegai is the largest registered owner, with 100.0%.

What is the revenue of SR RØR OG BAD AS?

SR RØR OG BAD AS had revenue of NOK 452,000 in 2025.

Who is the general manager of SR RØR OG BAD AS?

Nahom Mekonen Tzegai is registered as general manager of SR RØR OG BAD AS.

Where is SR RØR OG BAD AS based?

SR RØR OG BAD AS has its business address in Skjetten.

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.