BIZTRAC BETA
Rental and operating of own or leased real estate

INTERIØR-GÅRDEN AS

Org. no. 983924859 Limited company (AS) Grimstad Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 6.8m
Operating profit NOK 2.9m
Equity NOK 10.0m
Incorporated 2001
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

INTERIØR-GÅRDEN AS is registered as a limited company in Grimstad, Agder with organisation number 983924859. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 1.0m, divided into 500 shares. The company's stated purpose is: “Oppføre forretningsbygg, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.8m in revenue and NOK 2.9m in operating profit.

Key figures · 2024

Revenue
NOK 6.8m
Operating profit
NOK 2.9m
Equity
NOK 10.0m
Est. value
NOK 11.0m

Financial health · 2024

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

Who owns INTERIØR-GÅRDEN AS?

YTTERVIK INVEST AS
INTERIØR-GÅRDEN AS
NOK 6.8m rev. · NOK 2.9m profit

INTERIØR-GÅRDEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INTERIØR-GÅRDEN AS

Who owns INTERIØR-GÅRDEN AS?

YTTERVIK INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of INTERIØR-GÅRDEN AS?

INTERIØR-GÅRDEN AS had revenue of NOK 6.8m in 2024.

Who is the general manager of INTERIØR-GÅRDEN AS?

Roald Yttervik is registered as general manager of INTERIØR-GÅRDEN AS.

Where is INTERIØR-GÅRDEN AS based?

INTERIØR-GÅRDEN AS has its business address in Grimstad.

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.