BIZTRAC BETA
Construction of residential and non-residential buildings

TINNBYGG EIENDOM AS

Org. no. 989278487 Limited company (AS) Tinn Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −1.3m
Equity NOK 890,000
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,3 mill kr).

TINNBYGG EIENDOM AS is registered as a limited company in Tinn, Telemark with organisation number 989278487. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og investere i aksjer i andre selskap samt forestå utbygging av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −1.3m in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −1.3m
Equity
NOK 890,000
Est. value
NOK 913,000

Financial health · 2024

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

Who owns TINNBYGG EIENDOM AS?

IVAR GRAVER
TINNBYGG EIENDOM AS
NOK 0 rev. · NOK −1.3m profit

TINNBYGG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TINNBYGG EIENDOM AS own?

TINNBYGG EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TINNBYGG EIENDOM AS

Who owns TINNBYGG EIENDOM AS?

IVAR GRAVER is the largest registered owner, with 100.0%.

What is the revenue of TINNBYGG EIENDOM AS?

TINNBYGG EIENDOM AS had revenue of NOK 0 in 2024.

Where is TINNBYGG EIENDOM AS based?

TINNBYGG EIENDOM AS has its business address in Tinn Austbygd.

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.