BIZTRAC BETA
Business and other management consultancy activities

KLØFTA REGNSKAP AS

Org. no. 966921706 Limited company (AS) Enebakk Incorporated 1993 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 706,000
Equity NOK 22.5m
Incorporated 1993
Share capital NOK 210,000

KLØFTA REGNSKAP AS is registered as a limited company in Enebakk, Akershus with organisation number 966921706. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1993. Registered share capital is NOK 210,000, divided into 2100 shares. The company's stated purpose is: “Forretningsmessig bedriftsrådgivning og annen administrativ rådgivning, investering i aksjer og annen kapitalforvaltning, samt å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 706,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 706,000
Equity
NOK 22.5m
Est. value
NOK 14.5m

Financial health · 2025

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

Who owns KLØFTA REGNSKAP AS?

BREDE HENRIK GJESTANG
KLØFTA REGNSKAP AS
NOK 1.3m rev. · NOK 706,000 profit

KLØFTA REGNSKAP AS has 3 registered shareholders:

All shareholders and roles →

Which companies does KLØFTA REGNSKAP AS own?

KLØFTA REGNSKAP AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KLØFTA REGNSKAP AS

Who owns KLØFTA REGNSKAP AS?

BREDE HENRIK GJESTANG is the largest registered owner, with 52.4%.

What is the revenue of KLØFTA REGNSKAP AS?

KLØFTA REGNSKAP AS had revenue of NOK 1.3m in 2025.

Where is KLØFTA REGNSKAP AS based?

KLØFTA REGNSKAP AS has its business address in Flateby.

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.