BIZTRAC BETA
Rental and operating of own or leased real estate

PP LANGMYRA 10 AS

Org. no. 918489738 Limited company (AS) Time Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 795,000
Equity NOK 797,000
Incorporated 2017
Share capital NOK 300,000

Signals

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

PP LANGMYRA 10 AS is registered as a limited company in Time, Rogaland with organisation number 918489738. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 300,000, divided into 100 shares. The company's stated purpose is: “Utleie bygg, kjøp, salg, utvikling og forvaltning av fast eiendom og alt som står i naturlig forbindelse med dette, herunder direkte og indirekte investeringer i foretak som driver slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 795,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 795,000
Equity
NOK 797,000
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns PP LANGMYRA 10 AS?

PLANUM AS
PP LANGMYRA 10 AS
NOK 1.1m rev. · NOK 795,000 profit

PP LANGMYRA 10 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PP LANGMYRA 10 AS

Who owns PP LANGMYRA 10 AS?

PLANUM AS is the largest registered owner, with 100.0%.

What is the revenue of PP LANGMYRA 10 AS?

PP LANGMYRA 10 AS had revenue of NOK 1.1m in 2025.

Where is PP LANGMYRA 10 AS based?

PP LANGMYRA 10 AS has its business address in Bryne.

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.