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

PYNTEN EIENDOM AS

Org. no. 985637016 Limited company (AS) Lillehammer Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 100,000
Incorporated 2003
Share capital NOK 100,000

Signals

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

PYNTEN EIENDOM AS is registered as a limited company in Lillehammer, Innlandet with organisation number 985637016. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å inneha grunnbokshjemmel til eiendommerne Gnr.54 og Bnr. 13, 39, 107, 111, 159, 238 og 239 i Lillehammer kommune.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Former names: NITELVA EIENDOM AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 100,000
▲ +0 %
Est. value
NOK 91,000

Financial health · 2025

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

Who owns PYNTEN EIENDOM AS?

PYNTEN EIENDOM AS
NOK 0 rev. · NOK 0 profit

PYNTEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PYNTEN EIENDOM AS

Who owns PYNTEN EIENDOM AS?

PYNTEN I BORETTSLAG is the largest registered owner, with 100.0%.

What is the revenue of PYNTEN EIENDOM AS?

PYNTEN EIENDOM AS had revenue of NOK 0 in 2025.

Where is PYNTEN EIENDOM AS based?

PYNTEN EIENDOM AS has its business address in Lillehammer.

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.