BIZTRAC BETA
Rental and operating of own or leased real estate

L. JENSEN EIENDOM AS

Org. no. 991288295 Limited company (AS) Kristiansand Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 425,000
Operating profit NOK 1,000
Equity NOK 2.9m
Incorporated 2007
Share capital NOK 100,000

L. JENSEN EIENDOM AS is registered as a limited company in Kristiansand, Agder with organisation number 991288295. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i og utvikling av fast eiendom for salg og utleie og alt som hermed står i forbindelse, herunder investering i aksjer og andeler i selskaper med samme formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 425,000 in revenue and NOK 1,000 in operating profit.

Key figures · 2025

Revenue
NOK 425,000
Operating profit
NOK 1,000
Equity
NOK 2.9m
Est. value
NOK 2.1m

Financial health · 2025

Liquidity
5.40
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
88.1%
Very good
Equity as a share of total capital

Who owns L. JENSEN EIENDOM AS?

TETRA HOLDING AS
L. JENSEN EIENDOM AS
NOK 425,000 rev. · NOK 1,000 profit

L. JENSEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about L. JENSEN EIENDOM AS

Who owns L. JENSEN EIENDOM AS?

TETRA HOLDING AS is the largest registered owner, with 60.0%.

What is the revenue of L. JENSEN EIENDOM AS?

L. JENSEN EIENDOM AS had revenue of NOK 425,000 in 2025.

Who is the general manager of L. JENSEN EIENDOM AS?

Frode Jensen is registered as general manager of L. JENSEN EIENDOM AS.

Where is L. JENSEN EIENDOM AS based?

L. JENSEN EIENDOM AS has its business address in Tveit.

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.