BIZTRAC BETA
Buying and selling of own real estate

POSTVEIEN 142 EIENDOM AS

Org. no. 933083543 Limited company (AS) Oslo Incorporated 1982 Active
Ownership graph ↗
Revenue 2024 NOK 6.6m
Operating profit NOK 5.2m
Equity NOK 4.6m
Incorporated 1982
Share capital NOK 1.8m

Signals

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

POSTVEIEN 142 EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 933083543. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 1982. Registered share capital is NOK 1.8m, divided into 800 shares. The company's stated purpose is: “Eie Postveien 142 A & B med gnr. 69, bnr. 906 med påstående bygninger og anlegg i Sandnes kommune, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.6m in revenue and NOK 5.2m in operating profit.

Key figures · 2024

Revenue
NOK 6.6m
Operating profit
NOK 5.2m
Equity
NOK 4.6m
Est. value
NOK 12.3m

Financial health · 2024

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

Who owns POSTVEIEN 142 EIENDOM AS?

POSTVEIEN 142 HOLDING AS
POSTVEIEN 142 EIENDOM AS
NOK 6.6m rev. · NOK 5.2m profit

POSTVEIEN 142 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about POSTVEIEN 142 EIENDOM AS

Who owns POSTVEIEN 142 EIENDOM AS?

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

What is the revenue of POSTVEIEN 142 EIENDOM AS?

POSTVEIEN 142 EIENDOM AS had revenue of NOK 6.6m in 2024.

Where is POSTVEIEN 142 EIENDOM AS based?

POSTVEIEN 142 EIENDOM AS has its business address in Oslo.

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.