BIZTRAC BETA
Rental and operating of own or leased real estate

SKOLEGATA AS

Org. no. 933823822 Limited company (AS) Meråker Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 20,000
Operating profit NOK −26,000
Equity NOK 4,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−26k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SKOLEGATA AS is registered as a limited company in Meråker, Trøndelag with organisation number 933823822. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie og forvalte fast eiendom med tilhørende aktiviteter, samt det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 20,000 in revenue and NOK −26,000 in operating profit.

Key figures · 2024

Revenue
NOK 20,000
Operating profit
NOK −26,000
Equity
NOK 4,000
Est. value
NOK 3,000

Financial health · 2024

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

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

Who owns SKOLEGATA AS?

GIMLE-AS
SKOLEGATA AS
NOK 20,000 rev. · NOK −26,000 profit

SKOLEGATA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKOLEGATA AS

Who owns SKOLEGATA AS?

GIMLE-AS is the largest registered owner, with 100.0%.

What is the revenue of SKOLEGATA AS?

SKOLEGATA AS had revenue of NOK 20,000 in 2024.

Where is SKOLEGATA AS based?

SKOLEGATA AS has its business address in Meråker.

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.