BIZTRAC BETA
COMPANY REGISTER PROFILE
994251406 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

TIKO EIGEDOM AS

Org. no. 994251406 Limited company (AS) Tysnes Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 569,000
Operating profit NOK 310,000
Equity NOK 2.6m
Incorporated 2009
Share capital NOK 500,000

TIKO EIGEDOM AS is registered as a limited company in Tysnes, Vestland with organisation number 994251406. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Investering i, utvikling og drift av fast eiendom, investering i andre selskap og hva som naturlig hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 569,000 in revenue and NOK 310,000 in operating profit.

Key figures · 2025

Revenue
NOK 569,000
▼ −6 %
Operating profit
NOK 310,000
▲ +38 %
Equity
NOK 2.6m
▲ +7 %
Est. value
NOK 2.4m

Financial health · 2025

Liquidity
6.03
Very good
Current assets ÷ current liabilities
Profitability
7.9%
Satisfactory
Return on total assets
Solidity
64.5%
Very good
Equity as a share of total capital

Who owns TIKO EIGEDOM AS?

TIKO EIGEDOM AS
NOK 569,000 rev. · NOK 310,000 profit

TIKO EIGEDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TIKO EIGEDOM AS

Who owns TIKO EIGEDOM AS?

KJARTAN HAGEN is the largest registered owner, with 50.0%.

What is the revenue of TIKO EIGEDOM AS?

TIKO EIGEDOM AS had revenue of NOK 569,000 in 2025.

Who is the general manager of TIKO EIGEDOM AS?

Kjartan Hagen is registered as general manager of TIKO EIGEDOM AS.

Where is TIKO EIGEDOM AS based?

TIKO EIGEDOM AS has its business address in Tysnes.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.