BIZTRAC BETA
Uoppgitt

VERDIGJENVINNING LOM OG SKJÅK AS

Org. no. 912616339 Limited company (AS) Lom Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 212,000
Incorporated 2013
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).

VERDIGJENVINNING LOM OG SKJÅK AS is registered as a limited company in Lom, Innlandet with organisation number 912616339. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2013. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Bidra til å realisere verdier ved konkurser og overtatte/tiltrådte eiendeler i selskap i/under avvikling, herunder yte tjenester i den forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 212,000
Est. value
NOK 249,000

Financial health · 2025

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

Who owns VERDIGJENVINNING LOM OG SKJÅK AS?

SPAREBANK 1 LOM OG SKJÅK
VERDIGJENVINNING LOM OG SKJÅK AS
NOK 0 rev. · NOK −10,000 profit

VERDIGJENVINNING LOM OG SKJÅK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VERDIGJENVINNING LOM OG SKJÅK AS

Who owns VERDIGJENVINNING LOM OG SKJÅK AS?

SPAREBANK 1 LOM OG SKJÅK is the largest registered owner, with 100.0%.

What is the revenue of VERDIGJENVINNING LOM OG SKJÅK AS?

VERDIGJENVINNING LOM OG SKJÅK AS had revenue of NOK 0 in 2025.

Where is VERDIGJENVINNING LOM OG SKJÅK AS based?

VERDIGJENVINNING LOM OG SKJÅK 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.