BIZTRAC BETA
Buying and selling of own real estate

KNEPPE VEST AS

Org. no. 927451328 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 5.2m
Operating profit NOK 3.7m
Equity NOK 711,000
Incorporated 2021
Share capital NOK 60,000

Signals

1 flags
  • Nylig endring 2026-04-17 Aksjekapital registrert 2026-04-17.

KNEPPE VEST AS is registered as a limited company in Trondheim, Trøndelag with organisation number 927451328. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2021. Registered share capital is NOK 60,000, divided into 50 shares. The company's stated purpose is: “Kjøpe, selge, eie, leie ut, utvikle og drifte fast eiendom herunder masseuttak og -deponering, samt eie aksjer og andeler i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.2m in revenue and NOK 3.7m in operating profit.

Key figures · 2025

Revenue
NOK 5.2m
Operating profit
NOK 3.7m
Equity
NOK 711,000
Est. value
NOK 7.9m

Financial health · 2025

Liquidity
0.83
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.4%
Satisfactory
Equity as a share of total capital

Who owns KNEPPE VEST AS?

VASSFJELLET AS
KNEPPE VEST AS
NOK 5.2m rev. · NOK 3.7m profit

KNEPPE VEST AS has 1 registered shareholder:

All shareholders and roles →

Group structure

KNEPPE VEST AS er morselskap for 56 datterselskaper:

Frequently asked questions about KNEPPE VEST AS

Who owns KNEPPE VEST AS?

VASSFJELLET AS is the largest registered owner, with 100.0%.

What is the revenue of KNEPPE VEST AS?

KNEPPE VEST AS had revenue of NOK 5.2m in 2025.

Who is the general manager of KNEPPE VEST AS?

Øyvind Antonsen is registered as general manager of KNEPPE VEST AS.

Where is KNEPPE VEST AS based?

KNEPPE VEST AS has its business address in Heimdal.

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.