BIZTRAC BETA
Construction of residential and non-residential buildings

K TOFT BYGG AS

Org. no. 963419244 Limited company (AS) Øygarden Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 16,000
Operating profit NOK 13,000
Equity NOK 85,000
Incorporated 1991
Share capital NOK 200,000

K TOFT BYGG AS is registered as a limited company in Øygarden, Vestland with organisation number 963419244. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1991. Registered share capital is NOK 200,000. The company's stated purpose is: “Erverv, planlegging og utbygging av boligområder/ tomter, bygging av hus for salg og tilhørende virksomheter, samt deltakelse i andre selskap. Levering av byggesett og bygging av hus på fremmede tomter.”. The most recent filed accounts, for the 2025 financial year, show NOK 16,000 in revenue and NOK 13,000 in operating profit.

Key figures · 2025

Revenue
NOK 16,000
Operating profit
NOK 13,000
Equity
NOK 85,000
Est. value
NOK 81,000

Financial health · 2025

Liquidity
2.00
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
49.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns K TOFT BYGG AS?

KÅRE AUDUN TOFT
K TOFT BYGG AS
NOK 16,000 rev. · NOK 13,000 profit

K TOFT BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about K TOFT BYGG AS

Who owns K TOFT BYGG AS?

KÅRE AUDUN TOFT is the largest registered owner, with 50.0%.

What is the revenue of K TOFT BYGG AS?

K TOFT BYGG AS had revenue of NOK 16,000 in 2025.

Who is the general manager of K TOFT BYGG AS?

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

Where is K TOFT BYGG AS based?

K TOFT BYGG 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 15.06.2026.

Report a problem

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