BIZTRAC BETA
COMPANY REGISTER PROFILE
936089305 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

GILSTAD ASSETS AS

Org. no. 936089305 Limited company (AS) Levanger Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 111,000
Operating profit NOK 49,000
Equity NOK 67,000
Incorporated 2025
Share capital NOK 30,000

GILSTAD ASSETS AS is registered as a limited company in Levanger, Trøndelag with organisation number 936089305. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering, forvaltning og annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 111,000 in revenue and NOK 49,000 in operating profit.

Key figures · 2025

Revenue
NOK 111,000
Operating profit
NOK 49,000
Equity
NOK 67,000
Est. value
NOK 181,000

Financial health · 2025

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

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

Who owns GILSTAD ASSETS AS?

PETER ISAK ØDEGAARD GILSTAD
GILSTAD ASSETS AS
NOK 111,000 rev. · NOK 49,000 profit

GILSTAD ASSETS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GILSTAD ASSETS AS

Who owns GILSTAD ASSETS AS?

PETER ISAK ØDEGAARD GILSTAD is the largest registered owner, with 100.0%.

What is the revenue of GILSTAD ASSETS AS?

GILSTAD ASSETS AS had revenue of NOK 111,000 in 2025.

Who is the general manager of GILSTAD ASSETS AS?

Peter Isak Ødegaard Gilstad is registered as general manager of GILSTAD ASSETS AS.

Where is GILSTAD ASSETS AS based?

GILSTAD ASSETS AS has its business address in Levanger.

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.