BIZTRAC BETA
COMPANY REGISTER PROFILE
934057104 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 02.09.2026
⚠ODALSHYTTA AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Rental and operating of own or leased real estate

ODALSHYTTA AS

Org. no. 934057104 Limited company (AS) Nord-Odal Incorporated 2024 In liquidation
Ownership graph ↗
Equity NOK 30,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

ODALSHYTTA AS is registered as a limited company in Nord-Odal, Innlandet with organisation number 934057104. 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: “Kjøp, salg og utleie av fast eiendom.”.

Key figures · 2024

Equity
NOK 30,000

Financial health · 2024

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

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

Who owns ODALSHYTTA AS?

ODALSHYTTA AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ODALSHYTTA AS

Who owns ODALSHYTTA AS?

Silje Ruud Nybakk is the largest registered owner, with 34.0%.

Where is ODALSHYTTA AS based?

ODALSHYTTA AS has its business address in Sagstua.

Property

Business address Hesbakken 46, 2120 Sagstua
Cadastral unit 3414-36/30/0/0
Building Enebolig · 2 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.