BIZTRAC BETA
Rental and operating of own or leased real estate

PAUL TERDAL EIENDOM AS

Org. no. 955663012 Limited company (AS) Bremanger Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 603,000
Operating profit NOK 144,000
Equity NOK 2.0m
Incorporated 1989
Share capital NOK 30,000

PAUL TERDAL EIENDOM AS is registered as a limited company in Bremanger, Vestland with organisation number 955663012. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1989. Registered share capital is NOK 30,000, divided into 1312 shares. The company's stated purpose is: “Eie og forvalte fast eiendom og løsøre. Selskapet kan herunder omsette, leie ut eller på andre måter forvalte selskapets eiendeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 603,000 in revenue and NOK 144,000 in operating profit.

Key figures · 2025

Revenue
NOK 603,000
Operating profit
NOK 144,000
Equity
NOK 2.0m
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns PAUL TERDAL EIENDOM AS?

MONICHA TERDAL
PAUL TERDAL EIENDOM AS
NOK 603,000 rev. · NOK 144,000 profit

PAUL TERDAL EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about PAUL TERDAL EIENDOM AS

Who owns PAUL TERDAL EIENDOM AS?

MONICHA TERDAL is the largest registered owner, with 25.0%.

What is the revenue of PAUL TERDAL EIENDOM AS?

PAUL TERDAL EIENDOM AS had revenue of NOK 603,000 in 2025.

Who is the general manager of PAUL TERDAL EIENDOM AS?

Evy Karin Terdal Moe is registered as general manager of PAUL TERDAL EIENDOM AS.

Where is PAUL TERDAL EIENDOM AS based?

PAUL TERDAL EIENDOM AS has its business address in Bremanger.

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.