BIZTRAC BETA
Other education activities

LEVE & BLOMSTRE AS

Org. no. 926838350 Limited company (AS) Vestby Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 151,000
Operating profit NOK −127,000
Equity NOK 131,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−127k kr).
  • Nylig endring 2026-03-14 Adresseendring registrert 2026-03-14.

LEVE & BLOMSTRE AS is registered as a limited company in Vestby, Akershus with organisation number 926838350. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Bidra til et bedre fysisk og psykisk miljø for mennesker og bedrifter.”. The most recent filed accounts, for the 2024 financial year, show NOK 151,000 in revenue and NOK −127,000 in operating profit.

Key figures · 2024

Revenue
NOK 151,000
Operating profit
NOK −127,000
Equity
NOK 131,000
Est. value
NOK 169,000

Financial health · 2024

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

Who owns LEVE & BLOMSTRE AS?

NINA HAUG EIDE
LEVE & BLOMSTRE AS
NOK 151,000 rev. · NOK −127,000 profit

LEVE & BLOMSTRE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEVE & BLOMSTRE AS

Who owns LEVE & BLOMSTRE AS?

NINA HAUG EIDE is the largest registered owner, with 100.0%.

What is the revenue of LEVE & BLOMSTRE AS?

LEVE & BLOMSTRE AS had revenue of NOK 151,000 in 2024.

Who is the general manager of LEVE & BLOMSTRE AS?

Nina Haug Eide is registered as general manager of LEVE & BLOMSTRE AS.

Where is LEVE & BLOMSTRE AS based?

LEVE & BLOMSTRE AS has its business address in Son.

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.