biztrac. BETA
COMPANY REGISTER PROFILE
924748826 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

TANI HOLDING AS

Org. no. 924748826 Limited company (AS) Enebakk Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 233,000
Equity NOK 484,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-07-23 Adresseendring registrert 2026-07-23.

TANI HOLDING AS is registered as a limited company in Enebakk, Akershus with organisation number 924748826. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, utleie og investering i eiendom og selskapet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 233,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
▲ +56 %
Operating profit
NOK 233,000
▲ +433 %
Equity
NOK 484,000
▲ +60 %
Est. value
NOK 863,000

Financial health · 2025

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
25.0%
Very good
Return on total assets
Solidity
43.5%
Very good
Equity as a share of total capital

Who owns TANI HOLDING AS?

TANI HOLDING AS
NOK 1.2m rev. · NOK 233,000 profit

TANI HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TANI HOLDING AS own?

TANI HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TANI HOLDING AS

Who owns TANI HOLDING AS?

Lord Trond Hoff is the largest registered owner, with 52.0%.

What is the revenue of TANI HOLDING AS?

TANI HOLDING AS had revenue of NOK 1.2m in 2025.

Where is TANI HOLDING AS based?

TANI HOLDING AS has its business address in Ytre Enebakk.

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

Report a problem

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