biztrac. BETA
COMPANY REGISTER PROFILE
920456472 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

LITRANE EIGEDOM AS

Org. no. 920456472 Limited company (AS) Øygarden Incorporated 2018 Active
Revenue 2025 NOK 0
Operating profit NOK −246,000
Equity NOK 797,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

LITRANE EIGEDOM AS is registered as a limited company in Øygarden, Vestland with organisation number 920456472. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg og utvikling av fritidseiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −246,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −246,000
▼ −642 %
Equity
NOK 797,000
▼ −0 %
Est. value
NOK 727,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-1.8%
Not satisfactory
Return on total assets
Solidity
11.4%
Satisfactory
Equity as a share of total capital

Who owns LITRANE EIGEDOM AS?

LITRANE EIGEDOM AS
NOK 0 rev. · NOK −246,000 profit

LITRANE EIGEDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LITRANE EIGEDOM AS

Who owns LITRANE EIGEDOM AS?

TAMANOR AS is the largest registered owner, with 100.0%.

What is the revenue of LITRANE EIGEDOM AS?

LITRANE EIGEDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of LITRANE EIGEDOM AS?

Konrad Sekkingstad is registered as general manager of LITRANE EIGEDOM AS.

Where is LITRANE EIGEDOM AS based?

LITRANE EIGEDOM AS has its business address in Fjell.

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.