BIZTRAC BETA
Rental and operating of own or leased real estate

PRE EIENDOM AS

Org. no. 988394254 Limited company (AS) Nordre Follo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK 2.0m
Equity NOK 41.3m
Incorporated 2005
Share capital NOK 601,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

PRE EIENDOM AS is registered as a limited company in Nordre Follo, Akershus with organisation number 988394254. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 601,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av fast eiendom samt investeringsvirksomhet forøvrig.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK 2.0m
Equity
NOK 41.3m
Est. value
NOK 33.7m

Financial health · 2024

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

Who owns PRE EIENDOM AS?

LANGSETER HOLDING AS
PRE EIENDOM AS
NOK 2.7m rev. · NOK 2.0m profit

PRE EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PRE EIENDOM AS

Who owns PRE EIENDOM AS?

LANGSETER HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of PRE EIENDOM AS?

PRE EIENDOM AS had revenue of NOK 2.7m in 2024.

Who is the general manager of PRE EIENDOM AS?

Tor Kristian Langseter is registered as general manager of PRE EIENDOM AS.

Where is PRE EIENDOM AS based?

PRE EIENDOM AS has its business address in Ski.

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.