BIZTRAC BETA
Development of building projects

TINDE BEITO AS

Org. no. 922238073 Limited company (AS) Nord-Fron Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 411,000
Operating profit NOK −432,000
Equity NOK 152,000
Incorporated 2019
Share capital NOK 500,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−432k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TINDE BEITO AS is registered as a limited company in Nord-Fron, Innlandet with organisation number 922238073. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 500,000, divided into 5000 shares. The company's stated purpose is: “Kjøp, opparbeidelse og salg av tomter, oppføring av fritidseiendommer og andre produkter/tjenester som naturlig hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 411,000 in revenue and NOK −432,000 in operating profit.

Key figures · 2024

Revenue
NOK 411,000
Operating profit
NOK −432,000
Equity
NOK 152,000
Est. value
NOK 139,000

Financial health · 2024

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

Who owns TINDE BEITO AS?

VENA FRITIDSEIENDOM AS
TINDE BEITO AS
NOK 411,000 rev. · NOK −432,000 profit

TINDE BEITO AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TINDE BEITO AS

Who owns TINDE BEITO AS?

VENA FRITIDSEIENDOM AS is the largest registered owner, with 80.2%.

What is the revenue of TINDE BEITO AS?

TINDE BEITO AS had revenue of NOK 411,000 in 2024.

Where is TINDE BEITO AS based?

TINDE BEITO AS has its business address in Vinstra.

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.