BIZTRAC BETA
Development of building projects

LINDETUNET AS

Org. no. 926735608 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 482,000
Operating profit NOK 36,000
Equity NOK −5.4m
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−5,4 mill kr).

LINDETUNET AS is registered as a limited company in Oslo, Oslo with organisation number 926735608. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Kjøp, salg og utvikling av fast eiendom, medvirke i andre selskaper innen samme virksomhet, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 482,000 in revenue and NOK 36,000 in operating profit.

Key figures · 2024

Revenue
NOK 482,000
Operating profit
NOK 36,000
Equity
NOK −5.4m
Est. value
NOK 386,000

Financial health · 2024

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

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

Who owns LINDETUNET AS?

G. CHRISTENSEN EIENDOM AS
LINDETUNET AS
NOK 482,000 rev. · NOK 36,000 profit

LINDETUNET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LINDETUNET AS

Who owns LINDETUNET AS?

G. CHRISTENSEN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of LINDETUNET AS?

LINDETUNET AS had revenue of NOK 482,000 in 2024.

Who is the general manager of LINDETUNET AS?

Knut Henning Iversen is registered as general manager of LINDETUNET AS.

Where is LINDETUNET AS based?

LINDETUNET AS has its business address in Oslo.

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.