BIZTRAC BETA
Rental and operating of own or leased real estate

TERNETANGEN EIENDOM AS

Org. no. 984658885 Limited company (AS) Bømlo Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 475,000
Equity NOK 107,000
Incorporated 2002
Share capital NOK 202,000

TERNETANGEN EIENDOM AS is registered as a limited company in Bømlo, Vestland with organisation number 984658885. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 202,000, divided into 200 shares. The company's stated purpose is: “Utvikling, tilrettelegging, utbygging og utleie av eiendommer og driftsløsøre, samt virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 475,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 475,000
Equity
NOK 107,000
Est. value
NOK 785,000

Financial health · 2024

Liquidity
0.75
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.2%
Not satisfactory
Equity as a share of total capital

Who owns TERNETANGEN EIENDOM AS?

FRODE INNVÆR
TERNETANGEN EIENDOM AS
NOK 1.7m rev. · NOK 475,000 profit

TERNETANGEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TERNETANGEN EIENDOM AS own?

TERNETANGEN EIENDOM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about TERNETANGEN EIENDOM AS

Who owns TERNETANGEN EIENDOM AS?

FRODE INNVÆR is the largest registered owner, with 100.0%.

What is the revenue of TERNETANGEN EIENDOM AS?

TERNETANGEN EIENDOM AS had revenue of NOK 1.7m in 2024.

Where is TERNETANGEN EIENDOM AS based?

TERNETANGEN EIENDOM AS has its business address in Rubbestadneset.

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.