BIZTRAC BETA
Development of building projects

LOMA AS

Org. no. 989072544 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 932,000
Operating profit NOK −1.2m
Equity NOK −7.0m
Incorporated 2005
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−7,0 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,2 mill kr).

LOMA AS is registered as a limited company in Trondheim, Trøndelag with organisation number 989072544. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Erverve, utvikle og drive fast eiendom, samt snekkervirksomhet knyttet til rehabilitering og husbygging. Videre delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 932,000 in revenue and NOK −1.2m in operating profit.

Key figures · 2024

Revenue
NOK 932,000
Operating profit
NOK −1.2m
Equity
NOK −7.0m

Financial health · 2024

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

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

Who owns LOMA AS?

LOMA HOLDING AS
LOMA AS
NOK 932,000 rev. · NOK −1.2m profit

LOMA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOMA AS

Who owns LOMA AS?

LOMA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LOMA AS?

LOMA AS had revenue of NOK 932,000 in 2024.

Who is the general manager of LOMA AS?

Jorodd Sve is registered as general manager of LOMA AS.

Where is LOMA AS based?

LOMA AS has its business address in Trondheim.

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.