biztrac. BETA
COMPANY REGISTER PROFILE
925861405 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Joinery installation

LOMUNDAL TRONDHEIM AS

Org. no. 925861405 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −22,000
Equity NOK 8,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−22k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LOMUNDAL TRONDHEIM AS is registered as a limited company in Bærum, Akershus with organisation number 925861405. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Rehabilitering av privat boligmasse og annet som står i forbindelse med dette. Samt deltakelse i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −22,000
▼ −9 %
Equity
NOK 8,000
▼ −67 %
Est. value
NOK 9,000

Financial health · 2025

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

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

Who owns LOMUNDAL TRONDHEIM AS?

LOMUNDAL TRONDHEIM AS
· NOK −22,000 profit

LOMUNDAL TRONDHEIM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOMUNDAL TRONDHEIM AS

Who owns LOMUNDAL TRONDHEIM AS?

LOMUNDAL OSLO AS is the largest registered owner, with 100.0%.

Who is the general manager of LOMUNDAL TRONDHEIM AS?

Amund Alexander Nordal is registered as general manager of LOMUNDAL TRONDHEIM AS.

Where is LOMUNDAL TRONDHEIM AS based?

LOMUNDAL TRONDHEIM AS has its business address in Fornebu.

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.