BIZTRAC BETA
Construction of residential and non-residential buildings

LJOSHEIM AS

Org. no. 828487752 Limited company (AS) Evje Og Hornnes Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −37,000
Equity NOK 12,000
Incorporated 2021
Share capital NOK 100,000

Signals

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

LJOSHEIM AS is registered as a limited company in Evje Og Hornnes, Agder with organisation number 828487752. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Oppføring og salg av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −37,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −37,000
Equity
NOK 12,000
Est. value
NOK 12,000

Financial health · 2025

Liquidity
1.42
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.8%
Weak
Equity as a share of total capital

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

Who owns LJOSHEIM AS?

BJØRNERO HOLDING AS
LJOSHEIM AS
NOK 0 rev. · NOK −37,000 profit

LJOSHEIM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LJOSHEIM AS er morselskap for 3 datterselskaper:

Frequently asked questions about LJOSHEIM AS

Who owns LJOSHEIM AS?

BJØRNERO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LJOSHEIM AS?

LJOSHEIM AS had revenue of NOK 0 in 2024.

Where is LJOSHEIM AS based?

LJOSHEIM AS has its business address in Evje.

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.