BIZTRAC BETA
Rental and operating of own or leased real estate

MANTIN EIENDOM AS

Org. no. 977075327 Limited company (AS) Holmestrand Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 4.5m
Operating profit NOK 965,000
Equity NOK 15.0m
Incorporated 1996
Share capital NOK 100,000

MANTIN EIENDOM AS is registered as a limited company in Holmestrand, Vestfold with organisation number 977075327. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Å eie, utvikle og drive fast eiendom samt drive konsulentvirksomhet innenfor fast eiendom, herunder også deltakelse i andre selskaper, og hva som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.5m in revenue and NOK 965,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.5m
Operating profit
NOK 965,000
Equity
NOK 15.0m
Est. value
NOK 11.7m

Financial health · 2024

Liquidity
0.78
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.2%
Good
Equity as a share of total capital

Who owns MANTIN EIENDOM AS?

MARTIN EIENDOM AS
MANTIN EIENDOM AS
NOK 4.5m rev. · NOK 965,000 profit

MANTIN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MANTIN EIENDOM AS own?

MANTIN EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MANTIN EIENDOM AS

Who owns MANTIN EIENDOM AS?

MARTIN EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of MANTIN EIENDOM AS?

MANTIN EIENDOM AS had revenue of NOK 4.5m in 2024.

Where is MANTIN EIENDOM AS based?

MANTIN EIENDOM AS has its business address in Holmestrand.

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.