BIZTRAC BETA
Plumbing installation

LOM & SKJÅK RØRSERVICE AS

Org. no. 929516672 Limited company (AS) Lom Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 22,000
Equity NOK −511,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−511k kr).

LOM & SKJÅK RØRSERVICE AS is registered as a limited company in Lom, Innlandet with organisation number 929516672. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rørleggerbedrift.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 22,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 22,000
Equity
NOK −511,000
Est. value
NOK 111,000

Financial health · 2024

Liquidity
0.40
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-124.3%
Weak
Equity as a share of total capital

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

Who owns LOM & SKJÅK RØRSERVICE AS?

ANDERS SKJELDEN
LOM & SKJÅK RØRSERVICE AS
NOK 2.1m rev. · NOK 22,000 profit

LOM & SKJÅK RØRSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOM & SKJÅK RØRSERVICE AS

Who owns LOM & SKJÅK RØRSERVICE AS?

ANDERS SKJELDEN is the largest registered owner, with 100.0%.

What is the revenue of LOM & SKJÅK RØRSERVICE AS?

LOM & SKJÅK RØRSERVICE AS had revenue of NOK 2.1m in 2024.

Who is the general manager of LOM & SKJÅK RØRSERVICE AS?

Anders Skjelden is registered as general manager of LOM & SKJÅK RØRSERVICE AS.

Where is LOM & SKJÅK RØRSERVICE AS based?

LOM & SKJÅK RØRSERVICE AS has its business address in Lom.

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.