BIZTRAC BETA
Development of building projects

KARLESTRAND GÅRD AS

Org. no. 926683160 Limited company (AS) Ørland Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −6,000
Equity NOK 128,000
Incorporated 2020
Share capital NOK 180,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).

KARLESTRAND GÅRD AS is registered as a limited company in Ørland, Trøndelag with organisation number 926683160. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 180,000, divided into 180 shares. The company's stated purpose is: “Å drive med eiendomsutvikling med aktiviteter som naturlig hører inn under dette. Selskapet kan også delta i andre selskaper, herunder drive med kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 128,000
Est. value
NOK 117,000

Financial health · 2024

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

Who owns KARLESTRAND GÅRD AS?

STEIN OLAV ALEXANDERSEN KARLESTRAND
KARLESTRAND GÅRD AS
NOK 0 rev. · NOK −6,000 profit

KARLESTRAND GÅRD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KARLESTRAND GÅRD AS

Who owns KARLESTRAND GÅRD AS?

STEIN OLAV ALEXANDERSEN KARLESTRAND is the largest registered owner, with 50.0%.

What is the revenue of KARLESTRAND GÅRD AS?

KARLESTRAND GÅRD AS had revenue of NOK 0 in 2024.

Where is KARLESTRAND GÅRD AS based?

KARLESTRAND GÅRD AS has its business address in Bjugn.

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.