BIZTRAC BETA
Rental and operating of own or leased real estate

T B EIENDOM AS

Org. no. 910452894 Limited company (AS) Lillehammer Incorporated 1969 Active
Ownership graph ↗
Revenue 2024 NOK 2.4m
Operating profit NOK −331,000
Equity NOK 19.8m
Incorporated 1969
Share capital NOK 240,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−331k kr).

T B EIENDOM AS is registered as a limited company in Lillehammer, Innlandet with organisation number 910452894. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1969. Registered share capital is NOK 240,000. The company's stated purpose is: “Eie og drive fast eiendom samt investere i andre driftsmidler og evt. verdipapirer, aksjer og virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK −331,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
Operating profit
NOK −331,000
Equity
NOK 19.8m
Est. value
NOK 21.9m

Financial health · 2024

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

Who owns T B EIENDOM AS?

JOHAN ERIK BELSVIK
T B EIENDOM AS
NOK 2.4m rev. · NOK −331,000 profit

T B EIENDOM AS has 6 registered shareholders:

All shareholders and roles →

Which companies does T B EIENDOM AS own?

T B EIENDOM AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about T B EIENDOM AS

Who owns T B EIENDOM AS?

JOHAN ERIK BELSVIK is the largest registered owner, with 27.5%.

What is the revenue of T B EIENDOM AS?

T B EIENDOM AS had revenue of NOK 2.4m in 2024.

Where is T B EIENDOM AS based?

T B EIENDOM AS has its business address in Lillehammer.

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.