biztrac. BETA
COMPANY REGISTER PROFILE
965440747 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Activities of adventure companies

KÅRE TOFT AS

Org. no. 965440747 Limited company (AS) Øygarden Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK −410,000
Equity NOK 1.5m
Incorporated 1992
Employees 9
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−410k kr).

KÅRE TOFT AS is registered as a limited company in Øygarden, Vestland with organisation number 965440747. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 1992 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 2000 shares. The company's stated purpose is: “Eie eiendommer, eiendomsutvikling, handel samt deltakelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK −410,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
▼ −1 %
Operating profit
NOK −410,000
▼ −707 %
Equity
NOK 1.5m
▼ −27 %
Est. value
NOK 3.8m

Financial health · 2025

Liquidity
0.91
Weak
Current assets ÷ current liabilities
Profitability
-8.5%
Not satisfactory
Return on total assets
Solidity
31.5%
Good
Equity as a share of total capital

Who owns KÅRE TOFT AS?

KÅRE TOFT AS
NOK 3.2m rev. · NOK −410,000 profit

KÅRE TOFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KÅRE TOFT AS

Who owns KÅRE TOFT AS?

Kjersti Toft is the largest registered owner, with 50.0%.

What is the revenue of KÅRE TOFT AS?

KÅRE TOFT AS had revenue of NOK 3.2m in 2025.

Who is the general manager of KÅRE TOFT AS?

Kåre Audun Toft is registered as general manager of KÅRE TOFT AS.

Where is KÅRE TOFT AS based?

KÅRE TOFT AS has its business address in Rong.

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.