BIZTRAC BETA
Buying and selling of own real estate

KNEPPE ØST AS

Org. no. 927451263 Limited company (AS) Melhus Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK −18,000
Incorporated 2021
Share capital NOK 50,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−18k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).

KNEPPE ØST AS is registered as a limited company in Melhus, Trøndelag with organisation number 927451263. 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 50,000, divided into 50 shares. The company's stated purpose is: “Kjøpe, selge, eie, leie ut, utvikle og drifte fast eiendom, samt eie aksjer og andeler i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK −18,000

Financial health · 2025

Liquidity
0.13
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-697.4%
Weak
Equity as a share of total capital

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

Who owns KNEPPE ØST AS?

MABOL HOLDING AS
KNEPPE ØST AS
NOK 0 rev. · NOK −14,000 profit

KNEPPE ØST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KNEPPE ØST AS

Who owns KNEPPE ØST AS?

MABOL HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KNEPPE ØST AS?

KNEPPE ØST AS had revenue of NOK 0 in 2025.

Who is the general manager of KNEPPE ØST AS?

Anders Bolland is registered as general manager of KNEPPE ØST AS.

Where is KNEPPE ØST AS based?

KNEPPE ØST AS has its business address in Ler.

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.