BIZTRAC BETA
Rental and operating of own or leased real estate

LUNDSLETTA 31 AS

Org. no. 895574562 Limited company (AS) Kristiansand Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 456,000
Operating profit NOK 448,000
Equity NOK 1.1m
Incorporated 2010
Share capital NOK 100,000

LUNDSLETTA 31 AS is registered as a limited company in Kristiansand, Agder with organisation number 895574562. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eiendomsutvikling og tomtesalg, samt hva herved står i forbindelse, herunder deltakelse i annen virksomhet ved aksjeeie eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 456,000 in revenue and NOK 448,000 in operating profit.

Key figures · 2025

Revenue
NOK 456,000
Operating profit
NOK 448,000
Equity
NOK 1.1m
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
0.17
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.8%
Satisfactory
Equity as a share of total capital

Who owns LUNDSLETTA 31 AS?

KRISTIANSAND MISJONSKIRKE SALEM
LUNDSLETTA 31 AS
NOK 456,000 rev. · NOK 448,000 profit

LUNDSLETTA 31 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LUNDSLETTA 31 AS own?

LUNDSLETTA 31 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LUNDSLETTA 31 AS

Who owns LUNDSLETTA 31 AS?

KRISTIANSAND MISJONSKIRKE SALEM is the largest registered owner, with 100.0%.

What is the revenue of LUNDSLETTA 31 AS?

LUNDSLETTA 31 AS had revenue of NOK 456,000 in 2025.

Where is LUNDSLETTA 31 AS based?

LUNDSLETTA 31 AS has its business address in Kristiansand S.

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.