BIZTRAC BETA
Rental and operating of own or leased real estate

K132 EIENDOM AS

Org. no. 925589144 Limited company (AS) Horten Incorporated 1977 Active
Ownership graph ↗
Revenue 2025 NOK 652,000
Operating profit NOK −272,000
Equity NOK −1.5m
Incorporated 1977
Share capital NOK 500,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,5 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−272k kr).

K132 EIENDOM AS is registered as a limited company in Horten, Vestfold with organisation number 925589144. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1977. Registered share capital is NOK 500,000. The company's stated purpose is: “eie, handel, utleie og drift av fast eiendom og løsøre samt eie og handel av aksjer og andre verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 652,000 in revenue and NOK −272,000 in operating profit.

Key figures · 2025

Revenue
NOK 652,000
Operating profit
NOK −272,000
Equity
NOK −1.5m

Financial health · 2025

Liquidity
3.52
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-42.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns K132 EIENDOM AS?

PÅL HANSEN
K132 EIENDOM AS
NOK 652,000 rev. · NOK −272,000 profit

K132 EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Group structure

K132 EIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about K132 EIENDOM AS

Who owns K132 EIENDOM AS?

PÅL HANSEN is the largest registered owner, with 45.0%.

What is the revenue of K132 EIENDOM AS?

K132 EIENDOM AS had revenue of NOK 652,000 in 2025.

Where is K132 EIENDOM AS based?

K132 EIENDOM AS has its business address in Skoppum.

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.