BIZTRAC BETA
Rental and operating of own or leased real estate

TINNOSET EIENDOM AS

Org. no. 961030684 Limited company (AS) Notodden Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK 1.8m
Equity NOK 8.0m
Incorporated 1991
Share capital NOK 900,000

TINNOSET EIENDOM AS is registered as a limited company in Notodden, Telemark with organisation number 961030684. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1991. Registered share capital is NOK 900,000, divided into 900 shares. The company's stated purpose is: “Eiendomsforvaltning samt annen næringsvirksomhet, herunder deltagelse i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK 1.8m
Equity
NOK 8.0m
Est. value
NOK 9.2m

Financial health · 2025

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

Who owns TINNOSET EIENDOM AS?

BJØRN ASGEIR ANDERSEN
TINNOSET EIENDOM AS
NOK 2.7m rev. · NOK 1.8m profit

TINNOSET EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TINNOSET EIENDOM AS own?

TINNOSET EIENDOM AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

TINNOSET EIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about TINNOSET EIENDOM AS

Who owns TINNOSET EIENDOM AS?

BJØRN ASGEIR ANDERSEN is the largest registered owner, with 100.0%.

What is the revenue of TINNOSET EIENDOM AS?

TINNOSET EIENDOM AS had revenue of NOK 2.7m in 2024.

Where is TINNOSET EIENDOM AS based?

TINNOSET EIENDOM AS has its business address in Gransherad.

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.