BIZTRAC BETA
Development of building projects

LUNDSKOGEN ØSTRE AS

Org. no. 999074820 Limited company (AS) Trondheim Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −24,000
Equity NOK −75,000
Incorporated 2012
Share capital NOK 150,000

Signals

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

LUNDSKOGEN ØSTRE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 999074820. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2012. Registered share capital is NOK 150,000, divided into 1500 shares. The company's stated purpose is: “Eiendomsutvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −24,000
Equity
NOK −75,000

Financial health · 2025

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

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

Who owns LUNDSKOGEN ØSTRE AS?

HØISETH GULLIKSTAD AS
LUNDSKOGEN ØSTRE AS
NOK 0 rev. · NOK −24,000 profit

LUNDSKOGEN ØSTRE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUNDSKOGEN ØSTRE AS

Who owns LUNDSKOGEN ØSTRE AS?

HØISETH GULLIKSTAD AS is the largest registered owner, with 25.0%.

What is the revenue of LUNDSKOGEN ØSTRE AS?

LUNDSKOGEN ØSTRE AS had revenue of NOK 0 in 2025.

Who is the general manager of LUNDSKOGEN ØSTRE AS?

Per Erik Austberg is registered as general manager of LUNDSKOGEN ØSTRE AS.

Where is LUNDSKOGEN ØSTRE AS based?

LUNDSKOGEN ØSTRE AS has its business address in Flatåsen.

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.