BIZTRAC BETA
Retail sale of books

SPIRITUALGARDENING AS

Org. no. 934145658 Limited company (AS) Time Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 82,000
Incorporated 2024
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).

SPIRITUALGARDENING AS is registered as a limited company in Time, Rogaland with organisation number 934145658. The business is classified under retail sale of books (NACE 47.610). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 4 shares. The company's stated purpose is: “Kursvirksomhet og forlag og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 82,000
Est. value
NOK 103,000

Financial health · 2025

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

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

Who owns SPIRITUALGARDENING AS?

BRITH LUNDEMOEN HANSEN
SPIRITUALGARDENING AS
NOK 0 rev. · NOK −10,000 profit

SPIRITUALGARDENING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SPIRITUALGARDENING AS

Who owns SPIRITUALGARDENING AS?

BRITH LUNDEMOEN HANSEN is the largest registered owner, with 50.0%.

What is the revenue of SPIRITUALGARDENING AS?

SPIRITUALGARDENING AS had revenue of NOK 0 in 2025.

Who is the general manager of SPIRITUALGARDENING AS?

Grethe Lundemoen Hansen is registered as general manager of SPIRITUALGARDENING AS.

Where is SPIRITUALGARDENING AS based?

SPIRITUALGARDENING AS has its business address in Bryne.

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.