biztrac. BETA
COMPANY REGISTER PROFILE
929476255 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other unspecified social services without accommodation

INN PÅ HOMNES TUN AS

Org. no. 929476255 Limited company (AS) Steinkjer Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 69,000
Equity NOK 99,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-07-28 Adresseendring registrert 2026-07-28.

INN PÅ HOMNES TUN AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 929476255. The business is classified under other unspecified social services without accommodation (NACE 88.996). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Inn på tunet tjenester og turisme.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 69,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
▲ +34 %
Operating profit
NOK 69,000
▲ +23 %
Equity
NOK 99,000
▲ +118 %
Est. value
NOK 357,000

Financial health · 2025

Liquidity
7.40
Very good
Current assets ÷ current liabilities
Profitability
79.7%
Very good
Return on total assets
Solidity
85.1%
Weak
Equity as a share of total capital

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

Who owns INN PÅ HOMNES TUN AS?

INN PÅ HOMNES TUN AS
NOK 1.0m rev. · NOK 69,000 profit

INN PÅ HOMNES TUN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INN PÅ HOMNES TUN AS

Who owns INN PÅ HOMNES TUN AS?

May-Helen Erdal is the largest registered owner, with 100.0%.

What is the revenue of INN PÅ HOMNES TUN AS?

INN PÅ HOMNES TUN AS had revenue of NOK 1.0m in 2025.

Where is INN PÅ HOMNES TUN AS based?

INN PÅ HOMNES TUN AS has its business address in Steinkjer.

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

Report a problem

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