BIZTRAC BETA
Other real estate activities on a fee or contract basis

NEDRE HOVIN EIENDOM AS

Org. no. 898256022 Limited company (AS) Os Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 3,000
Equity NOK 98,000
Incorporated 2012
Share capital NOK 100,000

NEDRE HOVIN EIENDOM AS is registered as a limited company in Os, Innlandet with organisation number 898256022. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og forvalte fast eiendom, herunder utbyggingsvirksomhet samt å være delaktig i tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 3,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 3,000
Equity
NOK 98,000
Est. value
NOK 72,000

Financial health · 2024

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

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

Who owns NEDRE HOVIN EIENDOM AS?

URSUS INVEST AS
NEDRE HOVIN EIENDOM AS
NOK 0 rev. · NOK 3,000 profit

NEDRE HOVIN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NEDRE HOVIN EIENDOM AS

Who owns NEDRE HOVIN EIENDOM AS?

URSUS INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of NEDRE HOVIN EIENDOM AS?

NEDRE HOVIN EIENDOM AS had revenue of NOK 0 in 2024.

Who is the general manager of NEDRE HOVIN EIENDOM AS?

Bent Ramberg is registered as general manager of NEDRE HOVIN EIENDOM AS.

Where is NEDRE HOVIN EIENDOM AS based?

NEDRE HOVIN EIENDOM AS has its business address in Tufsingdalen.

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.